Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 06:18 UTC

redis / redis-py

Redis Python client

PythonMIT★ 13,647 stars⑂ 2,748 forkssince Nov 2009View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

redis/redis-py holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Vitality (99/100) and lowest on Security (56/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

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

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

Ownership

RedisOrganization · verified domain
2,961 followers79 public repossince Mar 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIredis8.1.0-16951 days agoredisdatabasekey-value-store

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
33.9/36Commit cadence — 49/52 weeks with commits
18/18Commit volume — 281 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year281
human_commit_share0.92
days_since_last_push1
active_weeks_last_year49

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 51 days ago
27/27Release cadence — a release every ~16.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv8.1.0
releases_from_tagsno
days_since_latest_release51
mean_days_between_releases16.2

Community & Adoption

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

92Excellent · 17% of overall
How it's scored
60/60Stars — 13,647 stars
25/25Forks — 2,748 forks
13.9/15Watchers — 314 watchers
Inputs used
forks2,748
stars13,647
watchers314
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesbadge.fury.io, codecov.io, github.com, readthedocs.org, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

86Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
13.7/22.5Commit distribution — top contributor authored 39% of commits
13.5/13.5Contributor breadth — 99 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.39
How it's scored
41.2/42Issue resolution — 98% of issues closed
22.3/30PR acceptance — 1,721/2,320 decided PRs merged
6/13Newcomer PR acceptance — 6/13 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs1,721
open_issues37
closed_issues1,905
prs_merged_7d5
prs_decided_7d7
prs_merged_30d29
prs_decided_30d45
issue_closed_ratio0.981
closed_unmerged_prs599
first_time_authors_30d10
first_time_prs_merged_30d6
first_time_prs_decided_30d13
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 2,961 followers of redis
25/25Track record — 79 public repos, account ~14 yr old
Inputs used
followers2,961
owner_typeOrganization
is_verifiedyes
owner_loginredis
public_repos79
account_age_days5,304

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://redis.readthedocs.io/en/latest/
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicspython, redis, redis-client, redis-cluster, redis-py
has_wikino
homepage—
docs_sitehttps://redis.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles
20/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsbenchmarks/requirements.txt, docs/requirements.txt, doctests/requirements.txt, pyproject.toml
has_codeql_workflowyes
has_security_policyno
has_dependabot_configyes

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
advisories6
affected_packages2
assessed_packages16
unassessed_packages28
affected_by_severitymoderate 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 16 resolved dependencies against OSV. 28 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.

97Exceptional · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://redis.io/llms.txt)
40/40Legible commit history — 90 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://redis.io/llms.txt
legible_history_share0.978
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes17,349
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — .mypy.ini, redis/py.typed
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs.mypy.ini, redis/py.typed
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0.08
How it's scored
27/45Type-checkable code — Python with type-check config (.mypy.ini, redis/py.typed)
49.7/55Manageable file sizes — 31/324 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes423,141
source_files_sampled324
oversized_source_files31
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

13,647GitHub stars
99contributors
281commits, last 12 months
1days since last push
100releases
3bus factor
37open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 25 authors (cap 12)
  • pypi download statistics for 'redis' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 2,748 ⇿
0Stars
2,748Forks
100Releases

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.

1,7502,0002,2502,5002,7502,748102020-112023-102026-09
Major 4Minor 18Patch 43

Each point covers 6 days.

Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPIasync-timeout>=4.0.3pyproject.toml
All dependencies 44

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

RegistryPackageVersionRelation
PyPIaiohttp—indirect
PyPIbuild1.2.2.post1indirect
PyPIclick8.3.3indirect
PyPIcoverage7.6.12indirect
PyPIcryptography—indirect
PyPIdocutils—indirect
PyPIfuro—indirect
PyPIhiredis—indirect
PyPIinvoke2.2.0indirect
PyPIipython—indirect
PyPInbsphinx—indirect
PyPInumpy—indirect
PyPIopentelemetry-api—indirect
PyPIopentelemetry-exporter-otlp-proto-grpc—indirect
PyPIopentelemetry-exporter-otlp-proto-http—indirect
PyPIopentelemetry-instrumentation-redis0.35b0indirect
PyPIopentelemetry-sdk—indirect
PyPIpackaging24.2indirect
PyPIpandas—indirect
PyPIpandoc—indirect
PyPIpybreaker—indirect
PyPIpyjwt—indirect
PyPIpyopenssl—indirect
PyPIpytest8.3.4indirect
PyPIpytest-asyncio1.1.0indirect
PyPIpytest-cov6.0.0indirect
PyPIpytest-forked—indirect
PyPIpytest-profiling1.8.1indirect
PyPIpytest-timeout2.3.1indirect
PyPIredis—indirect
PyPIredis4.3.4indirect
PyPIredis-entraid1.2.1indirect
PyPIrequests—indirect
PyPIruff0.9.6indirect
PyPIsentence-transformers—indirect
PyPIsphinx—indirect
PyPIsphinx-autodoc-typehints—indirect
PyPIsphinx-gallery—indirect
PyPItabulate—indirect
PyPIujson—indirect
PyPIuptrace1.14.0indirect
PyPIvulture—indirect
PyPIxxhash—indirect
PyPIxxhash3.6.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
pytest8.3.4indirectmoderate29.0.3
redis4.3.4indirectmoderate44.5.4

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.