Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 10:32 UTC

netromdk / vermin

Concurrently detect the minimum Python versions needed to run code

PythonMIT★ 541 stars⑂ 37 forkssince Feb 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

netromdk/vermin holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on AI Readiness (47/100). It was last updated 22 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

netromPersonal account
60 followers93 public repossince Nov 2013@luxionkeyshot

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 publishTags
PyPIvermin1.9.2475,4416028 days agoversiondetectionanalysisastdevelopment

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
28.8/36Push recency — last push 22 days ago
7.6/36Commit cadence — 11/52 weeks with commits
18/18Commit volume — 101 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year101
human_commit_share0.88
days_since_last_push22
active_weeks_last_year11
How it's scored
27/27Ships releases — 59 releases published
36/36Release recency — latest release 28 days ago
12.6/27Release cadence — a release every ~169 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count59
latest_release_tagv1.9.2
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases169
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?

71Good · 17% of overall
How it's scored
44.3/60Stars — 541 stars
13/25Forks — 37 forks
0/15Watchers — 2 watchers
Inputs used
forks37
stars541
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
75.7/80Monthly downloads — 475,441 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvermin
dependents—
ecosystemspypi
total_downloads—
monthly_downloads475,441
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 20 contributors
10/10OpenSSF Scorecard: Contributors — project has 7 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.954
How it's scored
40.7/42Issue resolution — 97% of issues closed
20.2/30PR acceptance — 184/273 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/9 approved changesets -- score normalized to 0
Inputs used
merged_prs184
open_issues3
closed_issues95
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.969
closed_unmerged_prs89
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.8/25Owner reach — 60 followers of netromdk
25/25Track record — 93 public repos, account ~13 yr old
Inputs used
followers60
owner_typeUser
is_verified—
owner_loginnetromdk
public_repos93
account_age_days4,745
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 28 days ago
20/20Version history — 60 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvermin
ecosystemspypi
any_deprecatedno
min_days_since_publish28

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
16/16Linter config — setup.cfg ([flake8])
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 12 topics
0/10Wiki
Inputs used
topicspython, python-2, python-3, parser, source-code-analysis, detection, version-checker, concurrency, multiprocessing, abstract-syntax-tree, ast, analysis
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practices — badge detected: InProgress
0/7.5Code-Review — Found 0/9 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 7 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories24
affected_packages7
assessed_packages30
unassessed_packages4
affected_by_severityhigh 2, moderate 4, low 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 30 resolved dependencies against OSV. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.8/40Legible commit history — 41 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.466
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — setup.cfg ([flake8])
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 12 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.12
How it's scored
0/45Type-checkable code — Python without a type-check config
48.9/55Manageable file sizes — 6/54 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes225,746
source_files_sampled54
oversized_source_files6

Key facts

541GitHub stars
20contributors
101commits, last 12 months
22days since last push
59releases
1bus factor
3open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 37 ⇿
0Stars
37Forks
57Releases

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.

01325383722018-032022-072026-11
Major 1Minor 17Patch 38

Each point covers 8 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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-11-17 10:32 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
0Code-ReviewFound 0/9 approved changesets -- score normalized to 0
10Contributorsproject has 7 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
All dependencies 34

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

RegistryPackageVersionRelation
PyPIastroid3.3.11indirect
PyPIbandit1.9.1indirect
PyPIbuild1.3.0indirect
PyPIcertifi2025.10.5indirect
PyPIcharset-normalizer3.4.3indirect
PyPIcoverage—indirect
PyPIcoveralls—indirect
PyPIdill0.4.0indirect
PyPIdocutils—indirect
PyPIdocutils0.22.2indirect
PyPIflake87.3.0indirect
PyPIidna3.10indirect
PyPIisort6.1.0indirect
PyPImarkdown-it-py4.0.0indirect
PyPImccabe0.7.0indirect
PyPImdurl0.1.2indirect
PyPIpackaging25.0indirect
PyPIplatformdirs4.5.0indirect
PyPIpycodestyle2.14.0indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.19.2indirect
PyPIpylint3.3.9indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpyroma5.0indirect
PyPIpyyaml6.0.3indirect
PyPIrequests2.32.5indirect
PyPIrich14.2.0indirect
PyPIsetuptools—indirect
PyPIsetuptools80.9.0indirect
PyPIstevedore5.5.0indirect
PyPItomlkit0.13.3indirect
PyPItrove-classifiers2025.9.11.17indirect
PyPIurllib32.5.0indirect
PyPIvulture2.14indirect
Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 30 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 0 are direct. 4 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
certifi2025.10.5indirecthigh22026.10.18
urllib32.5.0indirecthigh122.8.0
idna3.10indirectmoderate23.15
pylint3.3.9indirectmoderate14.0.9
requests2.32.5indirectmoderate22.33.0
setuptools80.9.0indirectmoderate384.1.0
pygments2.19.2indirectlow22.20.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI.