Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 23:13 UTC

redis / jedis

Redis Java client

JavaMIT★ 12,357 stars⑂ 3,916 forkssince Jun 2010View on GitHub ↗

redis/jedis holds a health index of 98 out of 100, placing it in the Exceptional band. It scores highest on Vitality (97/100) and lowest on Security (76/100). It was last updated today. 3 contributors account for most of its recent work.

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

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

Ownership

RedisOrganization · verified domain
2,909 followers78 public repossince Mar 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenredis.clients:jedis8.0.0-14417 days ago

Metrics by category

Vitality

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

97Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
31.2/36Commit cadence45/52 weeks with commits
18/18Commit volume240 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 27 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year240
human_commit_share0.86
days_since_last_push0
active_weeks_last_year45

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 17 days ago
27/27Release cadencea release every ~26.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv8.0.0
releases_from_tagsno
days_since_latest_release17
mean_days_between_releases26.2
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?

90Excellent · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars12,357 stars
25/25Forks3,916 forks
15/15Watchers660 watchers
Inputs used
forks3,916
stars12,357
watchers660
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno

Sustainability & Governance

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

88Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
16/22.5Commit distributiontop contributor authored 29% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 24 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.291
How it's scored
40.4/42Issue resolution96% of issues closed
21.5/30PR acceptance1,803/2,516 decided PRs merged
8.7/13Newcomer PR acceptance4/6 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 17/28 approved changesets -- score normalized to 6
Inputs used
merged_prs1,803
open_issues77
closed_issues1,898
prs_merged_7d8
prs_decided_7d10
prs_merged_30d29
prs_decided_30d36
issue_closed_ratio0.961
closed_unmerged_prs713
first_time_authors_30d5
first_time_prs_merged_30d4
first_time_prs_decided_30d6
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
24.9/25Owner reach2,909 followers of redis
25/25Track record78 public repos, account ~14 yr old
Inputs used
followers2,909
owner_typeOrganization
is_verifiedyes
owner_loginredis
public_repos78
account_age_days5,281

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on maven
35/35Publish recencylatest publish 17 days ago
20/20Version history144 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesredis.clients:jedis
ecosystemsmaven
any_deprecatedno
min_days_since_publish17

Engineering Quality

Are baseline engineering and documentation practices in place?

81Excellent · 19% of overall
How it's scored
24/24CI workflows14 workflow(s)
24/24Tests present
0/16Linter config
0/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_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://redis.github.io/jedis/
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsredis, java, jedis, redis-client, redis-cluster
has_wikiyes
homepagehttps://redis.github.io/jedis/
docs_sitehttps://redis.github.io/jedis/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
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
4.5/7.5Code-ReviewFound 17/28 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 24 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 27 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
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities48 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
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 maven:redis.clients:jedis@8.0.0 runtime dependency closure — what installing the published package pulls in — 6 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.

91Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://redis.io/llms.txt)
40/40Legible commit history84 of 86 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.977
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,367
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingJava (statically typed)
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice14 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance14 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_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.14
toolchain_manifestspom.xml
dependency_bot_commit_share0.14
How it's scored
45/45Type-checkable codeJava (statically typed)
54.2/55Manageable file sizes16/1,100 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes420,149
source_files_sampled1,100
oversized_source_files16
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

12,357GitHub stars
99contributors
240commits, last 12 months
0days since last push
100releases
3bus factor
77open issues
Maven, 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 12357 stars today.

More detail

Star and fork history 12,346 ★ / 3,916 ⇿
12,346Stars
3,916Forks
90Releases

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.

2,5005,0007,50010,00012,50012,3463,9161082020-022023-052026-08
Major 5Minor 17Patch 29

Each point covers 6 days.

OpenSSF Scorecard 7.0 / 10
7.0aggregate

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-27 23:12 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
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
6Code-ReviewFound 17/28 approved changesets -- score normalized to 6
10Contributorsproject has 24 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 27 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
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities48 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Mavenorg.junit:junit-bom${junit.version}pom.xml
Mavenorg.slf4j:slf4j-api${slf4j.version}pom.xml
Mavenorg.apache.commons:commons-pool22.13.1pom.xml
Mavenorg.json:json20260719pom.xml
Mavencom.google.code.gson:gson2.14.0pom.xml
Mavenredis.clients.authentication:redis-authx-core0.1.1-beta2pom.xml
Mavenio.github.resilience4j:resilience4j-all${resilience4j.version}pom.xml
Mavenio.github.resilience4j:resilience4j-circuitbreaker${resilience4j.version}pom.xml
Mavenio.github.resilience4j:resilience4j-retry${resilience4j.version}pom.xml
All dependencies 39

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

RegistryPackageVersionRelation
Mavencom.google.code.gson:gson2.14.0direct
Mavenio.github.resilience4j:resilience4j-all1.7.1direct
Mavenio.github.resilience4j:resilience4j-circuitbreaker1.7.1direct
Mavenio.github.resilience4j:resilience4j-retry1.7.1direct
Mavenorg.apache.commons:commons-pool22.13.1direct
Mavenorg.json:json20260719direct
Mavenorg.junit:junit-bom5.14.4direct
Mavenorg.slf4j:slf4j-api1.7.36direct
Mavenredis.clients.authentication:redis-authx-core0.1.1-beta2direct
Mavench.qos.logback:logback-classic1.2.13indirect
Mavencom.fasterxml.jackson.core:jackson-databind2.22.1indirect
Mavencom.fasterxml.jackson.datatype:jackson-datatype-jsr3102.22.1indirect
Mavencom.kohlschutter.junixsocket:junixsocket-core2.11.0indirect
Maveneu.rekawek.toxiproxy:toxiproxy-java2.1.11indirect
Mavennet.javacrumbs.json-unit:json-unit2.40.1indirect
Mavennet.revelc.code.formatter:formatter-maven-plugin2.16.0indirect
Mavenorg.apache.felix:maven-bundle-plugin5.1.9indirect
Mavenorg.apache.httpcomponents.client5:httpclient5-fluent5.6.3indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.15.0indirect
Mavenorg.awaitility:awaitility4.3.0indirect
Mavenorg.codehaus.mojo:build-helper-maven-plugin3.6.1indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.6.3indirect
Mavenorg.hamcrest:hamcrest3.0indirect
Mavenorg.jacoco:jacoco-maven-plugin0.8.15indirect
Mavenorg.junit.jupiter:junit-jupiter-apiindirect
Mavenorg.junit.jupiter:junit-jupiter-engineindirect
Mavenorg.junit.jupiter:junit-jupiter-paramsindirect
Mavenorg.locationtech.jts:jts-core1.20.0indirect
Mavenorg.mockito:mockito-inline4.11.0indirect
Mavenorg.mockito:mockito-junit-jupiter4.11.0indirect
Mavenorg.openjdk.jmh:jmh-core1.37indirect
Mavenorg.openjdk.jmh:jmh-generator-annprocess1.37indirect
Mavenorg.sonatype.central:central-publishing-maven-plugin0.11.0indirect
Mavenredis.clients.authentication:redis-authx-entraid0.1.1-beta2indirect
PyPImkdocsindirect
PyPImkdocs-glightboxindirect
PyPImkdocs-macros-pluginindirect
PyPImkdocs-materialindirect
PyPIpymdown-extensionsindirect
Dependency advisories 0

Installing maven:redis.clients:jedis@8.0.0 pulls in 6 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 statisticsMaven.