Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 00:56 UTC

freeeve / roaringrange

Rust · GoMIT★ 0 stars⑂ 0 forkssince May 2026View on GitHub ↗
KindLibraryApplicationhow this is determined

freeeve/roaringrange holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on AI Readiness (78/100) and lowest on Community & Adoption (24/100). It was last updated 51 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

48
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 49 is calibrated to 48 on the published index scale (record calibration 2026-08-02).

Ownership

Eve FreemanPersonal account
133 followers201 public repossince Jun 2011

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Gogithub.com/freeeve/roaringrangev0.42.0-6951 days ago
PyPIroaringrange0.42.0-2451 days agosearchfull-textroaringstatic-siteserverless

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

67Good · 21% of overall
How it's scored
18/36Push recencylast push 51 days ago
5.5/36Commit cadence8/52 weeks with commits
18/18Commit volume384 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year384
human_commit_share1
days_since_last_push51
active_weeks_last_year8
How it's scored
27/27Ships releases19 releases published
36/36Release recencylatest release 51 days ago
27/27Release cadencea release every ~0.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count19
latest_release_tagv0.42.0
releases_from_tagsno
days_since_latest_release51
mean_days_between_releases0.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

24At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, goreportcard.com, pkg.go.dev, snyk.io, sonarcloud.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

42Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.3/25Owner reach133 followers of freeeve
25/25Track record201 public repos, account ~15 yr old
Inputs used
followers133
owner_typeUser
is_verified
owner_loginfreeeve
public_repos201
account_age_days5,548
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go, pypi
35/35Publish recencylatest publish 51 days ago
20/20Version history69 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/freeeve/roaringrange, roaringrange
ecosystemsgo, pypi
any_deprecatedno
min_days_since_publish51

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionno

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

38Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): CI-Tests. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

78Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes305
How it's scored
12.6/18One-command bootstrapconformance/go.mod, examples/hybrid-search-lambda/Cargo.toml, examples/openalex/builder/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingpython/python_src/roaringrange/py.typed
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, go.sum
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configspython/python_src/roaringrange/py.typed
agent_commit_share0
toolchain_manifestsconformance/go.mod, examples/hybrid-search-lambda/Cargo.toml, examples/openalex/builder/Cargo.toml, examples/openalex/go.mod, examples/search-lambda/Cargo.toml, examples/term-search-lambda/Cargo.toml, go.mod, python/Cargo.toml, rust/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
52.5/55Manageable file sizes8/177 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes153,737
source_files_sampled177
oversized_source_files8
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

0GitHub stars
1contributors
384commits, last 12 months
51days since last push
19releases
1bus factor
0open issues
crates.io, Go, PyPIpackage ecosystems

Data collection warnings

  • Could not fetch crates package 'roaringrange' from its registry
  • Could not fetch crates package 'roaringrange-python' from its registry
  • pypi download statistics for 'roaringrange' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.8 / 10
3.8aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-06 00:56 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
Gogithub.com/RoaringBitmap/roaring/v2v2.14.4conformance/go.mod
Gogithub.com/freeeve/roaringrangev0.0.0conformance/go.mod
Gogithub.com/freeeve/roaringsearchv0.5.9conformance/go.mod
Gogithub.com/RoaringBitmap/roaring/v2v2.14.4go.mod
Gogithub.com/freeeve/fst-gov0.1.0go.mod
Gogithub.com/freeeve/go-ivfpqv0.1.0go.mod
Gogithub.com/freeeve/go-stemmersv0.0.0-20260606195828-3c78df9017f5go.mod
Gogithub.com/klauspost/compressv1.18.6go.mod
crates.iopyo30.22python/Cargo.toml
crates.ioroaring0.11python/Cargo.toml
crates.ioroaringrange_corepython/Cargo.toml
crates.ioroaring0.11rust/Cargo.toml
crates.iounicode-general-category1rust/Cargo.toml
crates.iounicode-normalization0.1rust/Cargo.toml
crates.iofutures0.3rust/Cargo.toml
crates.iofstrust/Cargo.toml
crates.iorust-stemmers1rust/Cargo.toml
crates.iowasm-bindgen0.2rust/Cargo.toml
crates.iowasm-bindgen-futures0.4rust/Cargo.toml
crates.iojs-sys0.3rust/Cargo.toml
crates.ioruzstd0.8rust/Cargo.toml
crates.ioweb-sys0.3rust/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo, PyPI.