Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-21 02:43 UTC

sphinx-contrib / sphinx-lint

Check for stylistic and formal issues in .rst and .py files included in the documentation

PythonCustom license★ 103 stars⑂ 27 forkssince Jan 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sphinx-contrib/sphinx-lint holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (78/100) and lowest on AI Readiness (33/100). It was last updated 14 days ago. 2 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

sphinx-contribOrganization
111 followers125 public repossince Sep 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIsphinx-lint1.0.2709,14024243 days ago

Metrics by category

Vitality

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

61Moderate · 21% of overall
How it's scored
28.8/36Push recencylast push 14 days ago
9.7/36Commit cadence14/52 weeks with commits
11.7/18Commit volume19 commits in the last year
5/10OpenSSF Scorecard: Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year19
human_commit_share
days_since_last_push14
active_weeks_last_year14
How it's scored
27/27Ships releases19 releases published
16.2/36Release recencylatest release 243 days ago
19.8/27Release cadencea release every ~91.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count19
latest_release_tagv1.0.2
releases_from_tagsno
days_since_latest_release243
mean_days_between_releases91.9
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?

60Moderate · 17% of overall
How it's scored
32.6/60Stars103 stars
11.8/25Forks27 forks
5/15Watchers9 watchers
Inputs used
forks27
stars103
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
78/80Monthly downloads709,140 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessphinx-lint
dependents
ecosystemspypi
total_downloads
monthly_downloads709,140
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12/22.5Commit distributiontop contributor authored 47% of commits
13.5/13.5Contributor breadth26 contributors
10/10OpenSSF Scorecard: Contributorsproject has 40 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled26
top_contributor_share0.466
How it's scored
22.1/42Issue resolution53% of issues closed
27.5/30PR acceptance78/85 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 21/27 approved changesets -- score normalized to 7
Inputs used
merged_prs78
open_issues36
closed_issues40
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.526
closed_unmerged_prs7
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
14.7/25Owner reach111 followers of sphinx-contrib
25/25Track record125 public repos, account ~8 yr old
Inputs used
followers111
owner_typeOrganization
is_verified
owner_loginsphinx-contrib
public_repos125
account_age_days3,232
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
26/35Publish recencylatest publish 243 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessphinx-lint
ecosystemspypi
any_deprecatedno
min_days_since_publish243

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter configtox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests17 out of 28 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://pypi.org/project/sphinx-lint/
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsdocs, documentation, lint, linter, python, sphinx, restructuredtext, rst
has_wikino
homepagehttps://pypi.org/project/sphinx-lint/
docs_sitehttps://pypi.org/project/sphinx-lint/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.5/2.5CI-Tests17 out of 28 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 21/27 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 40 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
3.8/7.5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
5/5Packagingpackaging workflow detected
3.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
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
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. 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_packages2
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:sphinx-lint@1.0.2 runtime dependency closure — what installing the published package pulls in — 2 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configtox.ini
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
7/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/13 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes20,147
source_files_sampled13
oversized_source_files0

Key facts

103GitHub stars
26contributors
19commits, last 12 months
14days since last push
19releases
2bus factor
36open issues
PyPIpackage ecosystems

More detail

OpenSSF Scorecard 6.2 / 10
6.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-07-21 02:43 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
6CI-Tests17 out of 28 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 21/27 approved changesets -- score normalized to 7
10Contributorsproject has 40 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIpolibpyproject.toml
PyPIregexpyproject.toml
All dependencies 2

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

RegistryPackageVersionRelation
PyPIpolibdirect
PyPIregexdirect
Dependency advisories 0

Installing pypi:sphinx-lint@1.0.2 pulls in 2 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.16.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.