Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-05 03:34 UTC

fmtlib / fmt

A modern formatting library

C++MIT★ 23,706 stars⑂ 2,943 forkssince Dec 2012View on GitHub ↗
KindMobile applicationhow this is determined

fmtlib/fmt holds a health index of 95 out of 100, placing it in the Exceptional band. It scores highest on Vitality (96/100) and lowest on AI Readiness (58/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

95
overall / 100
Exceptional

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.

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

Ownership

155 followers5 public repossince Apr 2014

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

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
33.9/36Commit cadence49/52 weeks with commits
18/18Commit volume381 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_year381
human_commit_share0.97
days_since_last_push1
active_weeks_last_year49

Release discipline

93Exceptional
How it's scored
27/27Ships releases58 releases published
36/36Release recencylatest release 49 days ago
19.8/27Release cadencea release every ~77.3 days
10/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count58
latest_release_tag12.2.0
releases_from_tagsno
days_since_latest_release49
mean_days_between_releases77.3

Community & Adoption

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

92Excellent · 17% of overall
How it's scored
60/60Stars23,706 stars
25/25Forks2,943 forks
13.9/15Watchers317 watchers
Inputs used
forks2,943
stars23,706
watchers317
growth_stateorganic
growth_factor_pct100

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesapi.securityscorecards.dev, github.com, shields.io, www.bestpractices.dev
has_pull_request_templateyes

Sustainability & Governance

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

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.1/22.5Commit distributiontop contributor authored 86% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.864
How it's scored
41.9/42Issue resolution100% of issues closed
21.3/30PR acceptance1,316/1,851 decided PRs merged
7/13Newcomer PR acceptance7/13 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 13/29 approved changesets -- score normalized to 4
Inputs used
merged_prs1,316
open_issues8
closed_issues2,999
prs_merged_7d5
prs_decided_7d5
prs_merged_30d10
prs_decided_30d19
issue_closed_ratio0.997
closed_unmerged_prs535
first_time_authors_30d9
first_time_prs_merged_30d7
first_time_prs_decided_30d13
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
15.8/25Owner reach155 followers of fmtlib
17.7/25Track record5 public repos, account ~12 yr old
Inputs used
followers155
owner_typeOrganization
is_verified
owner_loginfmtlib
public_repos5
account_age_days4,496
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows9 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
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://fmt.dev
10/10Repository description
10/10Topics12 topics
0/10Wiki
Inputs used
topicsformatting, printf, output, chrono, performance, multiplatform, cross-platform, cpp, ranges, floating-point, unicode, c-plus-plus
has_wikino
homepagehttps://fmt.dev
docs_sitehttps://fmt.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

91Excellent · 16% of overall

Security posture

89Excellent
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practicesbadge detected: Passing
3/7.5Code-ReviewFound 13/29 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 24 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate 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
0/5Packagingno data
4.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
7.5/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate8.9
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages39
unassessed_packages0
affected_by_severitymoderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 39 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.8/40Legible commit history47 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.485
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapsupport/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC++ (statically typed)
0/10Reproducible environment
6/10Demonstrated agent practice3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance3 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.03
toolchain_manifestssupport/build.gradle
dependency_bot_commit_share0.03
How it's scored
45/45Type-checkable codeC++ (statically typed)
49.3/55Manageable file sizes8/77 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes532,839
source_files_sampled77
oversized_source_files8

Key facts

23,706GitHub stars
99contributors
381commits, last 12 months
1days since last push
58releases
1bus factor
8open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 23706 stars today.
  • First-time contributor figures cover 12 of 15 authors (cap 12)

More detail

Star and fork history 23,676 ★ / 2,943 ⇿
23,676Stars
2,943Forks
16Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-21. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

04,0008,00012,00016,00020,00024,00023,6762,943372023-072025-012026-08
Major 2Minor 6Patch 8

Each point covers 3 days.

OpenSSF Scorecard 8.9 / 10
8.9aggregate

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-05 03:33 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests14 out of 14 merged PRs checked by a CI test -- score normalized to 10
5CII-Best-Practicesbadge detected: Passing
4Code-ReviewFound 13/29 approved changesets -- score normalized to 4
10Contributorsproject has 24 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
10Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 39

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

RegistryPackageVersionRelation
PyPIbabel2.18.0indirect
PyPIbackrefs7.0indirect
PyPIcertifi2026.5.20indirect
PyPIcharset-normalizer3.4.7indirect
PyPIclick8.4.1indirect
PyPIcmakelang0.6.13indirect
PyPIcolorama0.4.6indirect
PyPIghp-import2.1.0indirect
PyPIidna3.17indirect
PyPIimportlib-metadata9.0.0indirect
PyPIimportlib-resources7.1.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown3.10.2indirect
PyPImarkupsafe3.0.3indirect
PyPImergedeep1.3.4indirect
PyPImike2.1.3indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocs-material9.7.0indirect
PyPImkdocs-material-extensions1.3.1indirect
PyPImkdocstrings1.0.0indirect
PyPIpackaging26.2indirect
PyPIpaginate0.5.7indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.10.0indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions10.21.3indirect
PyPIpyparsing3.3.2indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrequests2.34.2indirect
PyPIsix1.17.0indirect
PyPItyping-extensions4.15.0indirect
PyPIurllib32.7.0indirect
PyPIverspec0.1.0indirect
PyPIwatchdog6.0.0indirect
PyPIzipp4.1.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 39 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
pymdown-extensions10.21.3indirectmoderate211.0.0

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