Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 22:09 UTC

tikv / rust-prometheus

Prometheus instrumentation library for Rust applications

RustApache-2.0★ 1,180 stars⑂ 208 forkssince Aug 2016View on GitHub ↗

tikv/rust-prometheus holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (80/100) and lowest on Vitality (20/100). It was last updated 225 days ago. 3 contributors account for most of its recent work.

63
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.

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

Ownership

TiKV ProjectOrganization
483 followers65 public repossince Jul 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioprometheus0.14.08,799,81341504 days agometricsprometheus
crates.ioprometheus-static-metric0.5.195,77282043 days ago

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 225 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year1
human_commit_share0.87
days_since_last_push225
active_weeks_last_year1
How it's scored
16.2/27Ships releases14 version tags (no GitHub releases)
7.2/36Release recencylatest release 504 days ago
12.6/27Release cadencea release every ~186 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagv0.14.0
releases_from_tagsyes
days_since_latest_release504
mean_days_between_releases186
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?

79Good · 17% of overall
How it's scored
49.8/60Stars1,180 stars
19.3/25Forks208 forks
9.6/15Watchers55 watchers
Inputs used
forks208
stars1,180
watchers55
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads8,895,585 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesprometheus, prometheus-static-metric
dependents
ecosystemscrates
total_downloads136,320,504
monthly_downloads8,895,585
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?

80Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15.7/22.5Commit distributiontop contributor authored 30% of commits
13.5/13.5Contributor breadth78 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled78
top_contributor_share0.303
How it's scored
26.7/42Issue resolution64% of issues closed
23.5/30PR acceptance277/353 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs277
open_issues66
closed_issues115
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.635
closed_unmerged_prs76
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
19.3/25Owner reach483 followers of tikv
25/25Track record65 public repos, account ~8 yr old
Inputs used
followers483
owner_typeOrganization
is_verified
owner_logintikv
public_repos65
account_age_days2,957
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable2 package(s) on crates
14/35Publish recencylatest publish 504 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesprometheus, prometheus-static-metric
ecosystemscrates
any_deprecatedno
min_days_since_publish504

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/prometheus
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/prometheus
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 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-Tests1 out of 30 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 20 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
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

65Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history87 of 87 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile, static-metric/Makefile
22/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 maintenance13 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_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, static-metric/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, static-metric/Cargo.toml
dependency_bot_commit_share0.13
How it's scored
45/45Type-checkable codeRust (statically typed)
54/55Manageable file sizes1/57 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes71,009
source_files_sampled57
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)proto/proto_model.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesproto/proto_model.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1,180GitHub stars
78contributors
1commits, last 12 months
225days since last push
14releases
3bus factor
66open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 208 ⇿
0Stars
208Forks
14Releases

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.

0408012016020024020542016-082021-082026-08
Major 0Minor 8Patch 5

Each point covers 10 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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 22:08 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-Tests1 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 13
RegistryPackageVersion constraintManifest
crates.iocfg-if^1.0Cargo.toml
crates.iofnv^1.0Cargo.toml
crates.iolazy_static^1.4Cargo.toml
crates.iolibc^0.2Cargo.toml
crates.ioparking_lot^0.12Cargo.toml
crates.ioprotobuf^3.7.2Cargo.toml
crates.iomemchr^2.3Cargo.toml
crates.ioreqwest^0.12Cargo.toml
crates.iothiserror^2.0Cargo.toml
crates.iosyn2.0static-metric/Cargo.toml
crates.ioproc-macro21.0static-metric/Cargo.toml
crates.ioquote1.0static-metric/Cargo.toml
crates.iolazy_static1.4static-metric/Cargo.toml
All dependencies 19

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

RegistryPackageVersionRelation
crates.iocfg-ifdirect
crates.iofnvdirect
crates.iolazy_staticdirect
crates.iolibcdirect
crates.iomemchrdirect
crates.ioparking_lotdirect
crates.ioproc-macro2direct
crates.ioprotobufdirect
crates.ioquotedirect
crates.ioreqwestdirect
crates.iosyndirect
crates.iothiserrordirect
crates.iocriterionindirect
crates.iogetoptsindirect
crates.iohyperindirect
crates.iohyper-utilindirect
crates.ioprocfsindirect
crates.ioprotobuf-codegenindirect
crates.iotokioindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.