Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 13:46 UTC

commonism / aiopenapi3

Python OpenAPI3 client/validator w\ {a,}syncio

PythonBSD-3-Clause★ 21 stars⑂ 8 forkssince Jan 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

commonism/aiopenapi3 holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (96/100) and lowest on AI Readiness (42/100). It was last updated today. 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

commonismPersonal account
24 followers66 public repossince Dec 2009

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
PyPIaiopenapi30.10.0161,09229148 days ago

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
15.9/36Commit cadence — 23/52 weeks with commits
18/18Commit volume — 138 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year138
human_commit_share0.93
days_since_last_push0
active_weeks_last_year23
How it's scored
27/27Ships releases — 20 releases published
27/36Release recency — latest release 148 days ago
19.8/27Release cadence — a release every ~87.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count20
latest_release_tagv0.10.0
releases_from_tagsno
days_since_latest_release148
mean_days_between_releases87.8
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?

50Moderate · 17% of overall
How it's scored
21.1/60Stars — 21 stars
7/25Forks — 8 forks
0/15Watchers — 2 watchers
Inputs used
forks8
stars21
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
0/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesgithub.com, readthedocs.org, shields.io
has_pull_request_templateno
How it's scored
69.4/80Monthly downloads — 161,092 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesaiopenapi3
dependents—
ecosystemspypi
total_downloads—
monthly_downloads161,092
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.8/22.5Commit distribution — top contributor authored 83% of commits
13.5/13.5Contributor breadth — 15 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.83
How it's scored
38.2/42Issue resolution — 91% of issues closed
19.1/30PR acceptance — 282/444 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs282
open_issues1
closed_issues10
prs_merged_7d2
prs_decided_7d2
prs_merged_30d11
prs_decided_30d11
issue_closed_ratio0.909
closed_unmerged_prs162
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
10.1/25Owner reach — 24 followers of commonism
25/25Track record — 66 public repos, account ~16 yr old
Inputs used
followers24
owner_typeUser
is_verified—
owner_logincommonism
public_repos66
account_age_days6,135
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 148 days ago
20/20Version history — 29 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaiopenapi3
ecosystemspypi
any_deprecatedno
min_days_since_publish148

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, pyproject.toml ([tool.ruff], [tool.black])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 14 out of 14 merged PRs checked by a CI test -- score normalized to 10
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 site — https://aiopenapi3.readthedocs.io/
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsopenapi3, openapi31, swagger, openapi, swagger2, python, async, asyncio, api, pydantic, openapi2, openapi32
has_wikiyes
homepage—
docs_sitehttps://aiopenapi3.readthedocs.io/
has_readmeyes
has_docs_diryes
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-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 14 out of 14 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/11 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.3
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages21
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:aiopenapi3@0.10.0 runtime dependency closure — what installing the published package pulls in — 21 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.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
4/40Legible commit history — 7 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.075
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — .pylintrc, pyproject.toml ([tool.ruff], [tool.black])
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
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_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/108 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes36,950
source_files_sampled108
oversized_source_files0

Key facts

21GitHub stars
15contributors
138commits, last 12 months
0days since last push
20releases
1bus factor
1open 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
17Releases

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.

1234567712022-042024-012025-09
Major 0Minor 6Patch 3

Each point covers 4 days.

OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-26 13:46 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
10CI-Tests14 out of 14 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/11 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIPyYaml—pyproject.toml
PyPIpydantic>= 2.13.0b2pyproject.toml
PyPIemail-validator—pyproject.toml
PyPIyarl—pyproject.toml
PyPIhttpx2—pyproject.toml
PyPImore-itertools—pyproject.toml
PyPItyping_extensions—pyproject.toml
PyPIjmespath—pyproject.toml
PyPIijson—pyproject.toml
PyPIjsonseq—pyproject.toml
All dependencies 67

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

RegistryPackageVersionRelation
PyPIemail-validator2.3.0direct
PyPIhttpx22.13.1direct
PyPIijson3.5.1direct
PyPIjmespath1.1.0direct
PyPIjsonseq1.0.0direct
PyPImore-itertools11.1.0direct
PyPIpydantic2.13.5direct
PyPIpyyaml6.0.3direct
PyPItyping-extensions4.16.0direct
PyPIyarl1.25.1direct
PyPI-—indirect
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.1indirect
PyPIasgiref3.12.1indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIblinker1.9.0indirect
PyPIbootstrap-flask2.6.0indirect
PyPIcffi2.1.1indirect
PyPIclick8.5.0indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.16.1indirect
PyPIcryptography50.0.1indirect
PyPIdnspython2.8.0indirect
PyPIexceptiongroup1.3.1indirect
PyPIfastapi0.141.1indirect
PyPIflask3.1.3indirect
PyPIflask-wtf1.3.0indirect
PyPIh110.16.0indirect
PyPIh24.4.1indirect
PyPIhpack4.2.0indirect
PyPIhttpcore22.13.1indirect
PyPIhttpx2-jsfetch1.0indirect
PyPIhttpx2-pytest2.0.0indirect
PyPIhyperframe6.1.0indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.0indirect
PyPIitsdangerous2.2.0indirect
PyPIjinja23.1.6indirect
PyPImarkupsafe3.0.3indirect
PyPImultidict6.9.1indirect
PyPInonecorn0.17.3indirect
PyPIpackaging26.3indirect
PyPIpluggy1.6.0indirect
PyPIpriority2.0.0indirect
PyPIpropcache0.5.4indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.5indirect
PyPIpydantic-extra-types2.11.1indirect
PyPIpygments2.21.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-multipart0.0.32indirect
PyPIsphinx-autodoc-typehints—indirect
PyPIsphinx-rtd-theme—indirect
PyPIstarlette1.7.0indirect
PyPItaskgroup0.2.2indirect
PyPItomli2.4.1indirect
PyPItrustme1.2.1indirect
PyPItruststore0.10.4indirect
PyPItyping-inspection0.4.4indirect
PyPIuvloop0.22.1indirect
PyPIwerkzeug3.1.8indirect
PyPIwsproto1.3.2indirect
PyPIwtforms3.2.2indirect
Dependency advisories 0

Installing pypi:aiopenapi3@0.10.0 pulls in 21 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.34.0 — full methodology · metrics wiki.

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