Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 21:52 UTC

metrics-rs / quanta

high-speed timing library in Rust

RustMIT★ 425 stars⑂ 46 forkssince Jan 2019View on GitHub ↗

metrics-rs/quanta holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (72/100) and lowest on AI Readiness (38/100). It was last updated 21 days ago. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

MetricsOrganization
48 followers5 public repossince Mar 2019

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioquanta0.12.67,999,99538429 days agonanosecondrdtsctiming

Metrics by category

Vitality

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

41Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 21 days ago
0.7/36Commit cadence1/52 weeks with commits
4.3/18Commit volume2 commits in the last year
2/10OpenSSF Scorecard: Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year2
human_commit_share0.94
days_since_last_push21
active_weeks_last_year1
How it's scored
16.2/27Ships releases32 version tags (no GitHub releases)
7.2/36Release recencylatest release 429 days ago
19.8/27Release cadencea release every ~117.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count32
latest_release_tagv0.12.6
releases_from_tagsyes
days_since_latest_release429
mean_days_between_releases117.3
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?

72Good · 17% of overall
How it's scored
42.6/60Stars425 stars
13.8/25Forks46 forks
4.3/15Watchers7 watchers
Inputs used
forks46
stars425
watchers7
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
13.5/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_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads7,999,995 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesquanta
dependents
ecosystemscrates
total_downloads135,428,192
monthly_downloads7,999,995
unverified_packages_excluded
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.8/22.5Commit distributiontop contributor authored 88% of commits
13.5/13.5Contributor breadth19 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled19
top_contributor_share0.876
How it's scored
31.3/42Issue resolution74% of issues closed
23.4/30PR acceptance46/59 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/29 approved changesets -- score normalized to 2
Inputs used
merged_prs46
open_issues13
closed_issues38
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.745
closed_unmerged_prs13
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
12.2/25Owner reach48 followers of metrics-rs
17.7/25Track record5 public repos, account ~7 yr old
Inputs used
followers48
owner_typeOrganization
is_verified
owner_loginmetrics-rs
public_repos5
account_age_days2,701
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on crates
14/35Publish recencylatest publish 429 days ago
20/20Version history38 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesquanta
ecosystemscrates
any_deprecatedno
min_days_since_publish429

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/quanta
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsrust-lang, timing, timestamp
has_wikino
homepage
docs_sitehttps://docs.rs/quanta
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 7/29 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
18.5/25Indirect dependencies free of known advisories2 affected: atty 0.2.14 (low), serde_cbor 0.11.2 (unknown)
36.4/40No advisories left outstanding2 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,866 days ago
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages83
unassessed_packages0
affected_by_severitylow 1, unknown 1
direct_affected_packages0
Matched the crates:quanta@0.12.6 runtime dependency closure — what installing the published package pulls in — 83 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.

38Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.5/40Legible commit history29 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.309
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.06
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/15 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes29,890
source_files_sampled15
oversized_source_files0

Key facts

425GitHub stars
19contributors
2commits, last 12 months
21days since last push
32releases
1bus factor
13open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 46 ⇿
0Stars
46Forks
32Releases

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.

010203040504422019-072023-012026-07
Major 0Minor 8Patch 22

Each point covers 7 days.

OpenSSF Scorecard 4.8 / 10
4.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-13 21:52 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
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 7/29 approved changesets -- score normalized to 2
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
crates.ioonce_cell1.4Cargo.toml
crates.ioprost-types0.11Cargo.toml
crates.iocrossbeam-utils0.8.5Cargo.toml
All dependencies 11

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

RegistryPackageVersionRelation
crates.iocrossbeam-utilsdirect
crates.ioonce_celldirect
crates.ioprost-typesdirect
crates.ioaverageindirect
crates.iocriterion0.3.3indirect
crates.iolibcindirect
crates.ioraw-cpuidindirect
crates.iowasiindirect
crates.iowasm-bindgen-testindirect
crates.ioweb-sysindirect
crates.iowinapiindirect
Dependency advisories 2

Installing crates:quanta@0.12.6 pulls in 83 packages, direct and transitive: 2 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
atty0.2.14indirectlow3
serde_cbor0.11.2indirectunknown1

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

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.31.0 — full methodology · metrics wiki.

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