Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 18:15 UTC

aio-libs / multidict

The multidict implementation

Python · C · C++Apache-2.0★ 490 stars⑂ 129 forkssince Feb 2016View on GitHub ↗

aio-libs/multidict holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (92/100) and lowest on AI Readiness (77/100). It was last updated today. 2 contributors account for most of its recent work.

96
overall / 100
Exceptional

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.

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

Ownership

aio-libsOrganization
1,200 followers68 public repossince Mar 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPImultidict6.7.1576,730,750149190 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume109 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year109
human_commit_share0.4
days_since_last_push0
active_weeks_last_year32
How it's scored
27/27Ships releases63 releases published
16.2/36Release recencylatest release 190 days ago
27/27Release cadencea release every ~27.9 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count63
latest_release_tagv6.7.1
releases_from_tagsno
days_since_latest_release190
mean_days_between_releases27.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

87Excellent · 17% of overall
How it's scored
43.6/60Stars490 stars
17.6/25Forks129 forks
6.2/15Watchers14 watchers
Inputs used
forks129
stars490
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, readthedocs.org, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads576,730,750 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmultidict
dependents
ecosystemspypi
total_downloads
monthly_downloads576,730,750
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?

78Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14/22.5Commit distributiontop contributor authored 38% of commits
13.5/13.5Contributor breadth59 contributors
10/10OpenSSF Scorecard: Contributorsproject has 60 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled59
top_contributor_share0.378
How it's scored
39.4/42Issue resolution94% of issues closed
23.7/30PR acceptance926/1,170 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 6/13 approved changesets -- score normalized to 4
Inputs used
merged_prs926
open_issues11
closed_issues166
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.938
closed_unmerged_prs244
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
22.1/25Owner reach1,200 followers of aio-libs
25/25Track record68 public repos, account ~12 yr old
Inputs used
followers1,200
owner_typeOrganization
is_verified
owner_loginaio-libs
public_repos68
account_age_days4,516
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on pypi
26/35Publish recencylatest publish 190 days ago
20/20Version history149 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmultidict
ecosystemspypi
any_deprecatedno
min_days_since_publish190

Engineering Quality

Are baseline engineering and documentation practices in place?

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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://multidict.aio-libs.org
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsaiohttp, multidict, headers, hacktoberfest
has_wikino
homepagehttps://multidict.aio-libs.org
docs_sitehttps://multidict.aio-libs.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 6/13 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 60 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.8
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages11
unassessed_packages2
affected_by_severitynone
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 11 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.

77Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history32 of 40 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.8
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes20,340
How it's scored
18/18One-command bootstrapMakefile, docs/Makefile
22/22Automated tests
11/11Lint / format config.flake8
11/11Static type checking.mypy.ini, multidict/py.typed
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance60 of the last 100 commits are automated dependency updates
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, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs.mypy.ini, multidict/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.6
How it's scored
27/45Type-checkable codePython with type-check config (.mypy.ini, multidict/py.typed)
53.8/55Manageable file sizes1/44 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes74,115
source_files_sampled44
oversized_source_files1

Key facts

490GitHub stars
59contributors
109commits, last 12 months
0days since last push
63releases
2bus factor
11open 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 ★ / 129 ⇿
0Stars
129Forks
63Releases

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.

025507510012515012942016-022021-052026-07
Major 5Minor 21Patch 33

Each point covers 10 days.

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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-04 18:14 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-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
4Code-ReviewFound 6/13 approved changesets -- score normalized to 4
10Contributorsproject has 60 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPItyping-extensions>= 4.1.0setup.cfg
All dependencies 13

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

RegistryPackageVersionRelation
PyPIcffiindirect
PyPIobjgraph3.6.2indirect
PyPIpre-commit4.6.1indirect
PyPIpsutil7.2.2indirect
PyPIpyenchant3.3.0indirect
PyPIpyperformance1.14.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-codspeed5.0.3indirect
PyPIpytest-cov7.1.0indirect
PyPIsphinx8.2.3indirect
PyPIsphinxcontrib-spelling8.0.2indirect
PyPIsphinxcontrib-towncrierindirect
PyPItowncrier25.8.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 11 packages, which also include development and test pins that never ship: 0 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.

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.30.0 — full methodology · metrics wiki.

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