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

grantjenks / python-diskcache

Python disk-backed cache (Django-compatible). Faster than Redis and Memcached. Pure-Python.

PythonCustom license★ 2,906 stars⑂ 184 forkssince Feb 2016View on GitHub ↗

grantjenks/python-diskcache holds a health index of 26 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (88/100) and lowest on Security (1/100). It was last updated 763 days ago. A single contributor accounts for most of its recent work.

26
overall / 100
At Risk

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.

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

Ownership

Grant JenksPersonal account
621 followers86 public repossince Aug 2009

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

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

17Critical · 21% of overall
How it's scored
0/36Push recency — last push 763 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push763
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 88 version tags (no GitHub releases)
0/36Release recency — latest release 1,108 days ago
19.8/27Release cadence — a release every ~105.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count88
latest_release_tagv5.6.3
releases_from_tagsyes
days_since_latest_release1,108
mean_days_between_releases105.6

Community & Adoption

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

64Moderate · 17% of overall
How it's scored
56.2/60Stars — 2,906 stars
18.9/25Forks — 184 forks
7.1/15Watchers — 20 watchers
Inputs used
forks184
stars2,906
watchers20
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
13.5/13.5Contributor breadth — 23 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.959
How it's scored
34.4/42Issue resolution — 82% of issues closed
17.9/30PR acceptance — 37/62 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs37
open_issues51
closed_issues229
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.818
closed_unmerged_prs25
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.1/25Owner reach — 621 followers of grantjenks
25/25Track record — 86 public repos, account ~17 yr old
Inputs used
followers621
owner_typeUser
is_verified—
owner_logingrantjenks
public_repos86
account_age_days6,230
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

88Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .pylintrc, tox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
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 — http://www.grantjenks.com/docs/diskcache/
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicspython, cache, persistence, key-value-store, filesystem
has_wikiyes
homepagehttp://www.grantjenks.com/docs/diskcache/
docs_sitehttp://www.grantjenks.com/docs/diskcache/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsrequirements-dev.txt, requirements.txt, setup.py
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.2/40Legible commit history — 6 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.06
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, tox.ini
11/11Static type checking — mypy.ini
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsmypy.ini
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (mypy.ini)
53.5/55Manageable file sizes — 1/36 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes81,956
source_files_sampled36
oversized_source_files1

Key facts

2,906GitHub stars
23contributors
0commits, last 12 months
763days since last push
88releases
1bus factor
51open 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-20: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 2906 stars today.
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 2,898 ★ / 184 ⇿
2,898Stars
184Forks
47Releases

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

05001,0001,5002,0002,5003,0002,898179982016-032021-062026-09
Major 3Minor 17Patch 27

Each point covers 10 days.

All dependencies 22

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

RegistryPackageVersionRelation
PyPIblue—indirect
PyPIcoverage—indirect
PyPIdjango4.2.*indirect
PyPIdjango-redis—indirect
PyPIdoc8—indirect
PyPIflake8—indirect
PyPIipython—indirect
PyPIjedi—indirect
PyPIpickledb—indirect
PyPIpylibmc—indirect
PyPIpylint—indirect
PyPIpytest—indirect
PyPIpytest-cov—indirect
PyPIpytest-django—indirect
PyPIpytest-env—indirect
PyPIpytest-xdist—indirect
PyPIrstcheck—indirect
PyPIsphinx—indirect
PyPIsqlitedict—indirect
PyPItox—indirect
PyPItwine—indirect
PyPIwheel—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.