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

aio-libs / aiocache

Asyncio cache manager for redis, memcached and memory

PythonBSD-3-Clause★ 1,437 stars⑂ 181 forkssince Sep 2016View on GitHub ↗

aio-libs/aiocache holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (89/100) and lowest on Vitality (40/100). It was last updated 75 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

aio-libsOrganization
1,216 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
PyPIaiocache0.12.3-43716 days ago

Metrics by category

Vitality

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

40Weak · 21% of overall
How it's scored
18/36Push recency — last push 75 days ago
6.9/36Commit cadence — 10/52 weeks with commits
10/18Commit volume — 12 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year12
human_commit_share0.19
days_since_last_push75
active_weeks_last_year10
How it's scored
27/27Ships releases — 22 releases published
7.2/36Release recency — latest release 716 days ago
12.6/27Release cadence — a release every ~260.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count22
latest_release_tagv0.12.3
releases_from_tagsno
days_since_latest_release716
mean_days_between_releases260.6

Community & Adoption

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

83Excellent · 17% of overall
How it's scored
51.2/60Stars — 1,437 stars
18.8/25Forks — 181 forks
6.4/15Watchers — 15 watchers
Inputs used
forks181
stars1,437
watchers15
growth_stateorganic
growth_factor_pct100

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-3-Clause)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, codecov.io, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9/22.5Commit distribution — top contributor authored 60% of commits
13.5/13.5Contributor breadth — 47 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled47
top_contributor_share0.6
How it's scored
36.8/42Issue resolution — 88% of issues closed
24.7/30PR acceptance — 603/732 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 6/7 approved changesets -- score normalized to 8
Inputs used
merged_prs603
open_issues39
closed_issues278
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.877
closed_unmerged_prs129
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
30/30Ownership backing — organization-owned
0/20Verified domain
22.2/25Owner reach — 1,216 followers of aio-libs
25/25Track record — 68 public repos, account ~12 yr old
Inputs used
followers1,216
owner_typeOrganization
is_verifiedno
owner_loginaio-libs
public_repos68
account_age_days4,554
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
14/35Publish recency — latest publish 716 days ago
20/20Version history — 43 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesaiocache
ecosystemspypi
any_deprecatedno
min_days_since_publish716

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .flake8, pyproject.toml ([tool.black])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 21 out of 30 merged PRs checked by a CI test -- score normalized to 7
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 site — http://aiocache.readthedocs.io
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicspython-3, asyncio, redis, memcached, cache, cachemanager
has_wikino
homepagehttp://aiocache.readthedocs.io
docs_sitehttp://aiocache.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
1.8/2.5CI-Tests — 21 out of 30 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 6/7 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 6 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/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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
advisories70
affected_packages4
assessed_packages17
unassessed_packages0
affected_by_severitycritical 1, high 1, moderate 2
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 17 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.

60Moderate · 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
llms_txt_url—
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
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — .flake8, pyproject.toml ([tool.black])
11/11Static type checking — .mypy.ini, aiocache/py.typed
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 81 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
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs.mypy.ini, aiocache/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.81
How it's scored
27/45Type-checkable code — Python with type-check config (.mypy.ini, aiocache/py.typed)
55/55Manageable file sizes — 0/56 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes25,151
source_files_sampled56
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

1,437GitHub stars
47contributors
12commits, last 12 months
75days since last push
22releases
1bus factor
39open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 1,435 ★ / 181 ⇿
1,435Stars
181Forks
21Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-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.

02505007501,0001,2501,5001,435174142016-112021-102026-08
Major 0Minor 10Patch 11

Each point covers 9 days.

OpenSSF Scorecard 5.1 / 10
5.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-09-12 09:56 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
7CI-Tests21 out of 30 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 6/7 approved changesets -- score normalized to 8
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities40 existing vulnerabilities detected
All dependencies 17

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

RegistryPackageVersionRelation
PyPIaiocache-dynamodb1.0.2indirect
PyPIaiohttp3.13.2indirect
PyPIaiomcache0.8.2indirect
PyPIflake87.3.0indirect
PyPIflake8-bandit4.1.1indirect
PyPIflake8-bugbear24.12.12indirect
PyPIflake8-import-order0.19.2indirect
PyPIflake8-requirements2.3.0indirect
PyPImarshmallow3.26.1indirect
PyPImsgpack1.1.2indirect
PyPImypy1.19.0indirect
PyPIpytest8.4.2indirect
PyPIpytest-asyncio1.2.0indirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-mock3.15.1indirect
PyPItypes-ujson5.10.0.20250822indirect
PyPIvalkey-glide2.4.0indirect
Dependency advisories 4

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

PackageVersionRelationSeverityAdvisoriesFixed in
aiohttp3.13.2indirectcritical643.14.3
msgpack1.1.2indirecthigh21.2.1
marshmallow3.26.1indirectmoderate24.1.2
pytest8.4.2indirectmoderate29.0.3

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.