Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 10:50 UTC

omnilib / stdlibs

What's in the Python stdlib

PythonMIT★ 12 stars⑂ 7 forkssince Mar 2021View on GitHub ↗

omnilib/stdlibs holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (89/100) and lowest on Community & Adoption (43/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

The Omnilib ProjectOrganization · verified domain
86 followers12 public repossince Apr 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIstdlibs2026.9.3-199 days ago

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 9 days ago
3.5/36Commit cadence — 5/52 weeks with commits
13.3/18Commit volume — 29 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year29
human_commit_share0.37
days_since_last_push9
active_weeks_last_year5
How it's scored
16.2/27Ships releases — 18 version tags (no GitHub releases)
36/36Release recency — latest release 9 days ago
19.8/27Release cadence — a release every ~110.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagv2026.9.3
releases_from_tagsyes
days_since_latest_release9
mean_days_between_releases110.2
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?

43Weak · 17% of overall
How it's scored
16.9/60Stars — 12 stars
6.5/25Forks — 7 forks
0/15Watchers — 2 watchers
Inputs used
forks7
stars12
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesreadthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

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

65Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.6/22.5Commit distribution — top contributor authored 71% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.707
How it's scored
42/42Issue resolution — 100% of issues closed
18.2/30PR acceptance — 114/188 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/11 approved changesets -- score normalized to 0
Inputs used
merged_prs114
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs74
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
13.9/25Owner reach — 86 followers of omnilib
20.1/25Track record — 12 public repos, account ~6 yr old
Inputs used
followers86
owner_typeOrganization
is_verifiedyes
owner_loginomnilib
public_repos12
account_age_days2,329

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .flake8
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 25 out of 26 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://stdlibs.omnilib.dev
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsstdlib, python, hacktoberfest, standard-library
has_wikiyes
homepagehttps://stdlibs.omnilib.dev
docs_sitehttps://stdlibs.omnilib.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.2/2.5CI-Tests — 25 out of 26 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/11 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 9 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
3.8/7.5Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
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
advisories18
affected_packages5
assessed_packages82
unassessed_packages2
affected_by_severitycritical 1, high 3, moderate 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 82 resolved dependencies against OSV. 2 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.

62Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.8/40Legible commit history — 20 of 37 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.541
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — makefile
22/22Automated tests
11/11Lint / format config — .flake8
11/11Static type checking — stdlibs/py.typed
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 63 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_filesmakefile
has_devcontainerno
has_linter_configyes
typecheck_configsstdlibs/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.63
How it's scored
27/45Type-checkable code — Python with type-check config (stdlibs/py.typed)
55/55Manageable file sizes — 0/32 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes12,507
source_files_sampled32
oversized_source_files0

Key facts

12GitHub stars
3contributors
29commits, last 12 months
9days since last push
18releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2025-07-19: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 12 stars today.
  • pypi download statistics for 'stdlibs' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 12 ★ / 7 ⇿
12Stars
7Forks
15Releases

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.

Star history is shown as collected on 2025-07-19. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02468101212722021-032023-052025-07
Major 0Minor 0Patch 15

Each point covers 4 days.

OpenSSF Scorecard 5.0 / 10
5.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-09-12 10:49 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests25 out of 26 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/11 approved changesets -- score normalized to 0
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow 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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities10 existing vulnerabilities detected
All dependencies 84

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

RegistryPackageVersionRelation
PyPIalabaster0.7.16indirect
PyPIalabaster1.0.0indirect
PyPIappdirs1.4.4indirect
PyPIast-serialize0.8.0indirect
PyPIattribution1.8.0indirect
PyPIattrs26.1.0indirect
PyPIbabel2.18.0indirect
PyPIblack25.11.0indirect
PyPIbuild—indirect
PyPIbuild1.4.4indirect
PyPIbuild1.6.0indirect
PyPIcertifi2026.7.22indirect
PyPIcharset-normalizer3.5.1indirect
PyPIclick8.1.8indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.10.7indirect
PyPIcoverage7.16.0indirect
PyPIdocutils0.21.2indirect
PyPIdocutils0.22.4indirect
PyPIfissix24.4.24indirect
PyPIflake87.3.0indirect
PyPIflit3.12.0indirect
PyPIflit4.0.2indirect
PyPIflit-core—indirect
PyPIflit-core4.0.2indirect
PyPIidna3.19indirect
PyPIimagesize1.5.0indirect
PyPIimagesize2.0.1indirect
PyPIimportlib-metadata8.7.1indirect
PyPIimportlib-metadata9.0.1indirect
PyPIjinja23.1.6indirect
PyPIlibcst1.9.0indirect
PyPIlibrt0.15.0indirect
PyPImarkupsafe3.0.3indirect
PyPImccabe0.7.0indirect
PyPImistune3.3.4indirect
PyPImoreorless0.6.0indirect
PyPImypy1.19.1indirect
PyPImypy2.3.1indirect
PyPImypy-extensions1.1.0indirect
PyPIpackaging26.2indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIpip26.0.1indirect
PyPIpip26.2.1indirect
PyPIplatformdirs4.11.7indirect
PyPIplatformdirs4.4.0indirect
PyPIpycodestyle2.14.0indirect
PyPIpyflakes3.4.0indirect
PyPIpygments2.21.0indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytokens0.4.1indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-ft8.0.0indirect
PyPIrequests2.32.5indirect
PyPIrequests2.34.2indirect
PyPIroman-numerals4.1.0indirect
PyPIsnowballstemmer3.1.1indirect
PyPIsphinx7.4.7indirect
PyPIsphinx8.1.3indirect
PyPIsphinx9.0.4indirect
PyPIsphinx9.1.0indirect
PyPIsphinx-mdinclude0.6.2indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItoml0.10.2indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItomlkit0.15.1indirect
PyPItrailrunner1.4.0indirect
PyPItyping-extensions4.16.0indirect
PyPIufmt2.8.0indirect
PyPIufmt2.9.1indirect
PyPIurllib32.6.3indirect
PyPIurllib32.7.0indirect
PyPIusort1.0.8.post1indirect
PyPIusort1.1.3indirect
PyPIzipp3.23.1indirect
PyPIzipp4.1.0indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
black25.11.0indirectcritical326.3.1
click8.1.8indirecthigh18.3.3
pip26.0.1indirecthigh826.2.0
urllib32.6.3indirecthigh42.7.0
requests2.32.5indirectmoderate22.33.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.