Public record
Software health reportschema 0.30.0 · metrics 2.5.0 · 2026-08-03 03:55 UTC

briansmith / ring

An experiment.

Assembly · RustCustom license★ 4,100 stars⑂ 796 forkssince Jul 2015View on GitHub ↗

briansmith/ring holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Community & Adoption (77/100) and lowest on Vitality (48/100). It was last updated 10 days ago. 2 contributors account for most of its recent work.

78
overall / 100
Good

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.

78
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 67 is calibrated to 78 on the published index scale (record calibration 2026-08-02).

Ownership

Brian SmithPersonal account
1,076 followers50 public repossince Jul 2008

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
crates.ioring0.17.1448,515,608133509 days agocryptocryptographyeccrandrsano-std

Metrics by category

Vitality

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

48Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 259 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year259
human_commit_share1
days_since_last_push10
active_weeks_last_year32
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

77Good · 17% of overall
How it's scored
58.6/60Stars — 4,100 stars
24.2/25Forks — 796 forks
9.2/15Watchers — 46 watchers
Inputs used
forks796
stars4,100
watchers46
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 48,515,608 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesring
dependents
ecosystemscrates
total_downloads651,190,362
monthly_downloads48,515,608
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.5/22.5Commit distribution — top contributor authored 44% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 64 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.444
How it's scored
41.3/42Issue resolution — 98% of issues closed
21/30PR acceptance — 1,246/1,779 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/18 approved changesets -- score normalized to 1
Inputs used
merged_prs1,246
open_issues16
closed_issues1,003
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.984
closed_unmerged_prs533
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
21.8/25Owner reach — 1,076 followers of briansmith
24.4/25Track record — 50 public repos, account ~18 yr old
Inputs used
followers1,076
owner_typeUser
is_verified
owner_loginbriansmith
public_repos50
account_age_days6,596
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on crates
14/35Publish recency — latest publish 509 days ago
20/20Version history — 133 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesring
ecosystemscrates
any_deprecatedno
min_days_since_publish509

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsrust, cryptography, security
has_wikino
homepage
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 17 out of 18 merged PRs checked by a CI test -- score normalized to 9
0.5/2.5CII-Best-Practices — badge detected: InProgress
0.8/7.5Code-Review — Found 2/18 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 64 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): branch_protection, packaging, signed_releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages59
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the crates:ring@0.17.14 runtime dependency closure — what installing the published package pulls in — 59 packages. Reachability is not analyzed.

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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 79 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.79
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — Cargo.toml, bench/Cargo.toml, build/bindgen/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, bench/Cargo.toml, build/bindgen/Cargo.toml, cavp/Cargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Assembly without a type-check config
54.5/55Manageable file sizes — 2/244 source files over 60KB
Inputs used
primary_languageAssembly
largest_source_bytes643,353
source_files_sampled244
oversized_source_files2

Key facts

4,100GitHub stars
100contributors
259commits, last 12 months
10days since last push
0releases
2bus factor
16open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'ring-cavp' from its registry
  • Could not fetch crates package 'ring-bench' from its registry

More detail

Star and fork history 0 ★ / 796 ⇿
0Stars
796Forks

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

012525037550062575069592015-082021-012026-07

Each point covers 11 days.

OpenSSF Scorecard 6.8 / 10
6.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-08-03 03:55 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests17 out of 18 merged PRs checked by a CI test -- score normalized to 9
2CII-Best-Practicesbadge detected: InProgress
1Code-ReviewFound 2/18 approved changesets -- score normalized to 1
10Contributorsproject has 64 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.iocfg-if1.0.0Cargo.toml
crates.iogetrandom0.4.3Cargo.toml
crates.iountrusted0.9Cargo.toml
crates.ioringbench/Cargo.toml
All dependencies 79

Full resolved dependency set from the GitHub dependency graph: 3 direct and 76 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
crates.iocfg-if1.0.1direct
crates.iogetrandom0.4.3direct
crates.iountrusted0.9.0direct
crates.ioaho-corasick1.1.3indirect
crates.ioalloca0.4.0indirect
crates.ioanes0.1.6indirect
crates.ioanstyle1.0.11indirect
crates.ioasync-trait0.1.89indirect
crates.ioautocfg1.5.0indirect
crates.iobumpalo3.19.0indirect
crates.iocast0.3.0indirect
crates.iocc1.2.57indirect
crates.iociborium0.2.2indirect
crates.iociborium-io0.2.2indirect
crates.iociborium-ll0.2.2indirect
crates.ioclap4.5.40indirect
crates.ioclap_builder4.5.40indirect
crates.ioclap_lex0.7.5indirect
crates.iocriterionindirect
crates.iocriterion0.8.2indirect
crates.iocriterion-plot0.8.2indirect
crates.iocrunchy0.2.4indirect
crates.ioeither1.15.0indirect
crates.iofind-msvc-tools0.1.9indirect
crates.iofutures-core0.3.32indirect
crates.iofutures-task0.3.32indirect
crates.iofutures-util0.3.32indirect
crates.iohalf2.6.0indirect
crates.ioitertools0.13.0indirect
crates.ioitoa1.0.15indirect
crates.iojs-sys0.3.91indirect
crates.iolibc0.2.174indirect
crates.iolibm0.2.16indirect
crates.iomemchr2.7.5indirect
crates.iominicov0.3.8indirect
crates.ionu-ansi-term0.50.3indirect
crates.ionum-traits0.2.19indirect
crates.ioonce_cell1.21.3indirect
crates.iooorandom11.1.5indirect
crates.iopage_size0.6.0indirect
crates.iopin-project-lite0.2.17indirect
crates.ioproc-macro21.0.95indirect
crates.ioquote1.0.40indirect
crates.ior-efi6.0.0indirect
crates.ioregex1.11.1indirect
crates.ioregex-automata0.4.9indirect
crates.ioregex-syntax0.8.5indirect
crates.iorustversion1.0.22indirect
crates.ioryu1.0.20indirect
crates.iosame-file1.0.6indirect
crates.ioserde1.0.228indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.228indirect
crates.ioserde_json1.0.140indirect
crates.ioshlex1.3.0indirect
crates.ioslab0.4.12indirect
crates.iosyn2.0.117indirect
crates.iotinytemplate1.2.1indirect
crates.iounicode-ident1.0.18indirect
crates.iowalkdir2.5.0indirect
crates.iowasm-bindgen0.2.114indirect
crates.iowasm-bindgen-futures0.4.64indirect
crates.iowasm-bindgen-macro0.2.114indirect
crates.iowasm-bindgen-macro-support0.2.114indirect
crates.iowasm-bindgen-shared0.2.114indirect
crates.iowasm-bindgen-testindirect
crates.iowasm-bindgen-test0.3.64indirect
crates.iowasm-bindgen-test-macro0.3.64indirect
crates.iowasm-bindgen-test-shared0.2.114indirect
crates.ioweb-sys0.3.91indirect
crates.iowinapi0.3.9indirect
crates.iowinapi-i686-pc-windows-gnu0.4.0indirect
crates.iowinapi-util0.1.11indirect
crates.iowinapi-x86_64-pc-windows-gnu0.4.0indirect
crates.iowindows-bindgenindirect
crates.iowindows-bindgen0.66.0indirect
crates.iowindows-link0.2.1indirect
crates.iowindows-sys0.61.2indirect
crates.iowindows-threading0.2.1indirect
Dependency advisories 0

Installing crates:ring@0.17.14 pulls in 59 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

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.5.0, schema v0.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.