Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-08 19:03 UTC

ludeeus / awesomeversion

One version package to rule them all, One version package to find them, One version package to bring them all, and in the darkness bind them.

PythonMIT★ 65 stars⑂ 8 forkssince Dec 2020View on GitHub ↗

ludeeus/awesomeversion holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Security (69/100) and lowest on AI Readiness (44/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

69
overall / 100
Good

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.

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

Ownership

Joakim SørensenPersonal account
702 followers108 public repossince Oct 2015@NabuCasa

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
PyPIawesomeversion25.8.01,772,51845370 days ago0verbuildvercalverpep440semverversion

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
15.9/36Commit cadence — 23/52 weeks with commits
16.8/18Commit volume — 74 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year74
human_commit_share0.15
days_since_last_push4
active_weeks_last_year23
How it's scored
27/27Ships releases — 45 releases published
7.2/36Release recency — latest release 370 days ago
12.6/27Release cadence — a release every ~125.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count45
latest_release_tag25.8.0
releases_from_tagsno
days_since_latest_release370
mean_days_between_releases125.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
29.3/60Stars — 65 stars
7/25Forks — 8 forks
1.7/15Watchers — 3 watchers
Inputs used
forks8
stars65
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,772,518 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesawesomeversion
dependents
ecosystemspypi
total_downloads
monthly_downloads1,772,518
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.4/22.5Commit distribution — top contributor authored 94% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.94
How it's scored
35/42Issue resolution — 83% of issues closed
24.8/30PR acceptance — 415/503 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs415
open_issues3
closed_issues15
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.833
closed_unmerged_prs88
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
20.5/25Owner reach — 702 followers of ludeeus
25/25Track record — 108 public repos, account ~10 yr old
Inputs used
followers702
owner_typeUser
is_verified
owner_loginludeeus
public_repos108
account_age_days3,953
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
14/35Publish recency — latest publish 370 days ago
20/20Version history — 45 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesawesomeversion
ecosystemspypi
any_deprecatedno
min_days_since_publish370

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://awesomeversion.ludeeus.dev
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://awesomeversion.ludeeus.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/2 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 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
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
5/5Packaging — packaging workflow detected
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): 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
advisories9
affected_packages5
assessed_packages35
unassessed_packages0
affected_by_severitycritical 1, high 2, moderate 1, 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 35 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
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
0/11Lint / format config
11/11Static type checking — awesomeversion/py.typed
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 85 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsawesomeversion/py.typed
agent_commit_share0.03
toolchain_manifests
dependency_bot_commit_share0.85
How it's scored
27/45Type-checkable code — Python with type-check config (awesomeversion/py.typed)
55/55Manageable file sizes — 0/40 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes18,291
source_files_sampled40
oversized_source_files0

Key facts

65GitHub stars
7contributors
74commits, last 12 months
4days since last push
45releases
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 ★ / 8 ⇿
0Stars
8Forks
24Releases

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.

02468812021-042023-062025-07
Major 0Minor 18Patch 6

Each point covers 4 days.

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-08 19:02 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
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
0Code-ReviewFound 0/2 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
10Packagingpackaging workflow detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
5Vulnerabilities5 existing vulnerabilities detected
All dependencies 35

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

RegistryPackageVersionRelation
PyPIastroid3.3.10indirect
PyPIawesomeversion0indirect
PyPIblack25.1.0indirect
PyPIcffi1.17.1indirect
PyPIclick8.1.8indirect
PyPIclick8.2.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.9.2indirect
PyPIdill0.4.0indirect
PyPIexceptiongroup1.3.0indirect
PyPIimportlib-metadata8.7.0indirect
PyPIiniconfig2.1.0indirect
PyPIisort6.0.1indirect
PyPImarkdown-it-py3.0.0indirect
PyPImccabe0.7.0indirect
PyPImdurl0.1.2indirect
PyPImypy1.16.1indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging25.0indirect
PyPIpathspec0.12.1indirect
PyPIplatformdirs4.3.8indirect
PyPIpluggy1.6.0indirect
PyPIpycparser2.22indirect
PyPIpygments2.19.2indirect
PyPIpylint3.3.7indirect
PyPIpytest8.4.1indirect
PyPIpytest-codspeed4.2.0indirect
PyPIpytest-cov6.2.1indirect
PyPIpytest-snapshot0.9.0indirect
PyPIpytest-timeout2.4.0indirect
PyPIrich14.0.0indirect
PyPItomli2.2.1indirect
PyPItomlkit0.13.3indirect
PyPItyping-extensions4.14.1indirect
PyPIzipp3.23.0indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
black25.1.0indirectcritical326.3.1
click8.1.8indirecthigh18.3.3
click8.2.1indirecthigh18.3.3
pytest8.4.1indirectmoderate29.0.3
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

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.5.0, schema v0.31.0 — full methodology · metrics wiki.

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