Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 04:08 UTC

samuelcolvin / python-devtools

Dev tools for python

PythonMIT★ 1,081 stars⑂ 50 forkssince Aug 2017View on GitHub ↗

samuelcolvin/python-devtools holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (84/100) and lowest on Vitality (18/100). It was last updated 542 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Samuel ColvinPersonal account
6,425 followers308 public repossince Apr 2013@pydantic

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIdevtools0.12.2-181051 days ago

Metrics by category

Vitality

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

18Critical · 21% of overall
How it's scored
0/36Push recencylast push 542 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 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_year0
human_commit_share
days_since_last_push542
active_weeks_last_year0
How it's scored
27/27Ships releases18 releases published
0/36Release recencylatest release 1,051 days ago
12.6/27Release cadencea release every ~125.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tagv0.12.2
releases_from_tagsno
days_since_latest_release1,051
mean_days_between_releases125.7
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
49.2/60Stars1,081 stars
14.1/25Forks50 forks
4.7/15Watchers8 watchers
Inputs used
forks50
stars1,081
watchers8
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
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

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.7/22.5Commit distributiontop contributor authored 79% of commits
13.5/13.5Contributor breadth14 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.791
How it's scored
27.3/42Issue resolution65% of issues closed
21.4/30PR acceptance67/94 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 7/25 approved changesets -- score normalized to 2
Inputs used
merged_prs67
open_issues22
closed_issues41
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.651
closed_unmerged_prs27
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach6,425 followers of samuelcolvin
25/25Track record308 public repos, account ~13 yr old
Inputs used
followers6,425
owner_typeUser
is_verified
owner_loginsamuelcolvin
public_repos308
account_age_days4,857
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
4/35Publish recencylatest publish 1,051 days ago
20/20Version history18 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdevtools
ecosystemspypi
any_deprecatedno
min_days_since_publish1,051

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://python-devtools.helpmanual.io/
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicspython-devtools, python, devtools
has_wikiyes
homepagehttps://python-devtools.helpmanual.io/
docs_sitehttps://python-devtools.helpmanual.io/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 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 23 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/25 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 11 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
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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_packages4
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:devtools@0.12.2 runtime dependency closure — what installing the published package pulls in — 4 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.

58Moderate · 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
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config
11/11Static type checkingdevtools/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configsdevtools/py.typed
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
27/45Type-checkable codePython with type-check config (devtools/py.typed)
55/55Manageable file sizes0/27 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes12,185
source_files_sampled27
oversized_source_files0
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 examplesexamples
Inputs used
example_dirsexamples
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

1,081GitHub stars
14contributors
0commits, last 12 months
542days since last push
18releases
1bus factor
22open issues
PyPIpackage ecosystems

More detail

Star and fork history 1,081 ★ / 0 ⇿
1,081Stars

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.

02004006008001,0001,2001,081542020-042023-052026-07

Each point covers 6 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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 04:07 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 23 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/25 approved changesets -- score normalized to 2
10Contributorsproject has 11 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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIexecuting>=1.1.1pyproject.toml
PyPIasttokens>=2.0.0,<3.0.0pyproject.toml
PyPIPygments>=2.15.0pyproject.toml
All dependencies 61

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

RegistryPackageVersionRelation
PyPIasttokensdirect
PyPIasttokens2.2.1direct
PyPIexecutingdirect
PyPIexecuting1.2.0direct
PyPIpygmentsdirect
PyPIpygments2.15.0direct
PyPIansi2html1.8.0indirect
PyPIasyncpg0.27.0indirect
PyPIattrs22.2.0indirect
PyPIblack23.3.0indirect
PyPIcertifi2023.7.22indirect
PyPIcharset-normalizer3.1.0indirect
PyPIclick8.1.3indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.2.2indirect
PyPIexceptiongroup1.1.1indirect
PyPIexceptiongroup1.1.3indirect
PyPIghp-import2.1.0indirect
PyPIidna3.4indirect
PyPIiniconfig2.0.0indirect
PyPIjinja23.1.2indirect
PyPImarkdown3.3.7indirect
PyPImarkdown-include0.7.0indirect
PyPImarkdown-include0.8.1indirect
PyPImarkdown-it-py2.2.0indirect
PyPImarkupsafe2.1.2indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.3.1indirect
PyPImkdocs1.4.2indirect
PyPImkdocs-exclude1.0.2indirect
PyPImkdocs-material8.3.9indirect
PyPImkdocs-material9.1.5indirect
PyPImkdocs-material-extensions1.1.1indirect
PyPImkdocs-simple-hooks0.1.5indirect
PyPImultidict6.0.4indirect
PyPImypy1.1.1indirect
PyPImypy-extensions1.0.0indirect
PyPInumpy1.24.2indirect
PyPIpackaging23.0indirect
PyPIpathspec0.11.1indirect
PyPIplatformdirs3.2.0indirect
PyPIpluggy1.0.0indirect
PyPIpydantic1.10.7indirect
PyPIpymdown-extensions10.0indirect
PyPIpytest7.2.2indirect
PyPIpytest-mock3.10.0indirect
PyPIpytest-pretty1.2.0indirect
PyPIpython-dateutil2.8.2indirect
PyPIpyyaml6.0indirect
PyPIpyyaml-env-tag0.1indirect
PyPIregex2023.3.23indirect
PyPIrequests2.31.0indirect
PyPIrich13.3.3indirect
PyPIruff0.0.261indirect
PyPIsix1.16.0indirect
PyPIsqlalchemy2.0.8indirect
PyPItomli2.0.1indirect
PyPItyping-extensions4.5.0indirect
PyPIurllib31.26.15indirect
PyPIwatchdog3.0.0indirect
Dependency advisories 0

Installing pypi:devtools@0.12.2 pulls in 4 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.17.0 — full methodology · metrics wiki.

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