Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 20:28 UTC

psf / black

The uncompromising Python code formatter

PythonMIT★ 41,777 stars⑂ 2,834 forkssince Mar 2018View on GitHub ↗
KindCommand-line toolLibraryPluginhow this is determined

psf/black holds a health index of 100 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (100/100) and lowest on AI Readiness (75/100). It was last updated today. 5 contributors account for most of its recent work.

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

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

Ownership

2,403 followers42 public repossince May 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIblack26.5.1-7378 days agoautomationautopep8formattergofmtpyfmtrustfmtyapf

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
31.8/36Commit cadence46/52 weeks with commits
18/18Commit volume282 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year282
human_commit_share0.77
days_since_last_push0
active_weeks_last_year46
How it's scored
27/27Ships releases55 releases published
36/36Release recencylatest release 78 days ago
19.8/27Release cadencea release every ~52.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count55
latest_release_tag26.5.1
releases_from_tagsno
days_since_latest_release78
mean_days_between_releases52.7

Community & Adoption

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

95Exceptional · 17% of overall
How it's scored
60/60Stars41,777 stars
25/25Forks2,834 forks
13/15Watchers223 watchers
Inputs used
forks2,834
stars41,777
watchers223
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, github.com, readthedocs.org, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

92Excellent · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
17.4/22.5Commit distributiontop contributor authored 23% of commits
13.5/13.5Contributor breadth97 contributors
10/10OpenSSF Scorecard: Contributorsproject has 87 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled97
top_contributor_share0.227
How it's scored
38/42Issue resolution90% of issues closed
24.1/30PR acceptance1,880/2,344 decided PRs merged
9.8/13Newcomer PR acceptance12/16 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 21/24 approved changesets -- score normalized to 8
Inputs used
merged_prs1,880
open_issues271
closed_issues2,543
prs_merged_7d14
prs_decided_7d14
prs_merged_30d33
prs_decided_30d38
issue_closed_ratio0.904
closed_unmerged_prs464
first_time_authors_30d8
first_time_prs_merged_30d12
first_time_prs_decided_30d16
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
24.3/25Owner reach2,403 followers of psf
23.9/25Track record42 public repos, account ~7 yr old
Inputs used
followers2,403
owner_typeOrganization
is_verified
owner_loginpsf
public_repos42
account_age_days2,639
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 78 days ago
20/20Version history73 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesblack
ecosystemspypi
any_deprecatedno
min_days_since_publish78

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows13 workflow(s)
24/24Tests present
16/16Linter config.flake8, tox.ini
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://black.readthedocs.io/en/stable/
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicspython, code, formatter, codeformatter, gofmt, yapf, autopep8, pre-commit-hook, hacktoberfest
has_wikiyes
homepagehttps://black.readthedocs.io/en/stable/
docs_sitehttps://black.readthedocs.io/en/stable/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

86Excellent · 16% of overall

Security posture

82Excellent
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6/7.5Code-ReviewFound 21/24 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 87 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 10 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
2.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
1/5SASTSAST tool is not run on all commits -- score normalized to 2
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate8.2
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
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 pypi:black@26.5.1 runtime dependency closure — what installing the published package pulls in — 6 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.

75Good · 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 history69 of 77 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.896
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapdocs/Makefile
22/22Automated tests
11/11Lint / format config.flake8, tox.ini
11/11Static type checkingsrc/black/py.typed
10/10Reproducible environmentDockerfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance20 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/black/py.typed
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0.2
How it's scored
27/45Type-checkable codePython with type-check config (src/black/py.typed)
53.4/55Manageable file sizes10/341 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes1,406,108
source_files_sampled341
oversized_source_files10
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 examplesnotebooks
Inputs used
example_dirsnotebooks
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

41,777GitHub stars
97contributors
282commits, last 12 months
0days since last push
55releases
5bus factor
271open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 15 authors (cap 12)

More detail

Star and fork history 0 ★ / 2,834 ⇿
0Stars
2,834Forks
28Releases

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.

1,5002,0002,5003,0002,834982023-042024-122026-08
Major 0Minor 18Patch 8

Each point covers 4 days.

OpenSSF Scorecard 8.2 / 10
8.2aggregate

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-04 20:28 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
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 21/24 approved changesets -- score normalized to 8
10Contributorsproject has 87 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 10 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
2SASTSAST tool is not run on all commits -- score normalized to 2
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
PyPIclick>=8.0.0pyproject.toml
PyPImypy-extensions>=0.4.3pyproject.toml
PyPIpackaging>=22.0pyproject.toml
PyPIpathspec>=1.0.0pyproject.toml
PyPIplatformdirs>=2pyproject.toml
PyPIpytokens~=0.4.0pyproject.toml
PyPItomli>=1.1.0pyproject.toml
PyPItyping-extensions>=4.0.1pyproject.toml
All dependencies 36

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

RegistryPackageVersionRelation
PyPIclickdirect
PyPImypy-extensionsdirect
PyPIpackagingdirect
PyPIpathspecdirect
PyPIplatformdirsdirect
PyPIpytokensdirect
PyPItomlidirect
PyPItyping-extensionsdirect
PyPIaiohttpindirect
PyPIcibuildwheel4.1.0indirect
PyPIcoloramaindirect
PyPIcoverageindirect
PyPIdocutils0.22.4indirect
PyPIfuro2025.12.19indirect
PyPIhatch1.15.1indirect
PyPIhatch-vcsindirect
PyPIhatchlingindirect
PyPIipythonindirect
PyPImypy0.920indirect
PyPImyst-parser5.1.0indirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIpytest-xdistindirect
PyPIsetuptools-scmindirect
PyPIsphinx9.1.0indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinxcontrib-programoutput0.20indirect
PyPItokenize-rtindirect
PyPItoxindirect
PyPItypes-dataclassesindirect
PyPItypes-typed-astindirect
PyPIuvloopindirect
PyPIvirtualenvindirect
PyPIwcwidth0.2.14indirect
PyPIwheelindirect
PyPIwinloopindirect
Dependency advisories 0

Installing pypi:black@26.5.1 pulls in 6 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

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