Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-26 22:32 UTC

rhubarbgroup / redis-cache

A persistent object cache backend for WordPress powered by Redis. Supports Predis, PhpRedis, Relay, replication, sentinels, clustering and WP-CLI.

PHPGPL-3.0★ 537 stars⑂ 159 forkssince Feb 2015View on GitHub ↗
KindPluginLibraryhow this is determined

rhubarbgroup/redis-cache holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on AI Readiness (45/100). It was last updated today. 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

Rhubarb GroupOrganization · verified domain
35 followers8 public repossince Apr 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistrhubarbgroup/redis-cache2.8.02,13090114 days agorediswordpress

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
10.4/36Commit cadence15/52 weeks with commits
14.7/18Commit volume42 commits in the last year
6/10OpenSSF Scorecard: Maintained6 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year42
human_commit_share0.95
days_since_last_push0
active_weeks_last_year15
How it's scored
27/27Ships releases90 releases published
27/36Release recencylatest release 114 days ago
19.8/27Release cadencea release every ~73.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count90
latest_release_tag2.8.0
releases_from_tagsno
days_since_latest_release114
mean_days_between_releases73.5
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?

62Moderate · 17% of overall
How it's scored
44.3/60Stars537 stars
18.3/25Forks159 forks
7.1/15Watchers20 watchers
Inputs used
forks159
stars537
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
44.4/80Monthly downloads2,130 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesrhubarbgroup/redis-cache
dependents1
ecosystemspackagist
total_downloads105,044
monthly_downloads2,130
unverified_packages_excluded

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.6/22.5Commit distributiontop contributor authored 75% of commits
13.5/13.5Contributor breadth63 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled63
top_contributor_share0.751
How it's scored
41.4/42Issue resolution98% of issues closed
23.8/30PR acceptance218/275 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/25 approved changesets -- score normalized to 1
Inputs used
merged_prs218
open_issues5
closed_issues326
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.985
closed_unmerged_prs57
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 backingorganization-owned
20/20Verified domain
11.2/25Owner reach35 followers of rhubarbgroup
18.9/25Track record8 public repos, account ~6 yr old
Inputs used
followers35
owner_typeOrganization
is_verifiedyes
owner_loginrhubarbgroup
public_repos8
account_age_days2,325

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 114 days ago
20/20Version history90 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrhubarbgroup/redis-cache
ecosystemspackagist
any_deprecatedno
min_days_since_publish114

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php, phpcs.xml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://wordpress.org/plugins/redis-cache/
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicswordpress-plugin, redis, predis, phpredis, php, cache, wordpress, relay
has_wikino
homepagehttps://wordpress.org/plugins/redis-cache/
docs_sitehttps://wordpress.org/plugins/redis-cache/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 3/25 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 15 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
4.5/7.5Maintained6 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://wordpress.org/llms.txt)
17.4/40Legible commit history31 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://wordpress.org/llms.txt
legible_history_share0.326
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php, phpcs.xml
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance5 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_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.05
How it's scored
0/45Type-checkable codePHP without a type-check config
54.7/55Manageable file sizes3/584 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes576,420
source_files_sampled584
oversized_source_files3

Key facts

537GitHub stars
63contributors
42commits, last 12 months
0days since last push
90releases
1bus factor
5open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 159 ⇿
0Stars
159Forks
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.

025507510012515014842015-082021-022026-08
Major 1Minor 12Patch 76

Each point covers 11 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-08-26 22:31 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during GetBranch(main): error during branchesHandler.query: 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
8CI-Tests16 out of 19 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/25 approved changesets -- score normalized to 1
10Contributorsproject has 15 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained6 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Packagistmnsami/composer-custom-directory-installer^2.0composer.json
Packagistpredis/predis^1.1 || ^2.0 || ^3.0composer.json
Packagistcolinmollenhour/credis^1.12.1composer.json
All dependencies 14

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

RegistryPackageVersionRelation
Packagistcolinmollenhour/credisdirect
Packagistmnsami/composer-custom-directory-installerdirect
Packagistpredis/predisdirect
Packagistcomposer/installersindirect
Packagistdealerdirect/phpcodesniffer-composer-installerindirect
Packagistdms/phpunit-arraysubset-assertsindirect
Packagistphpindirect
Packagistphp-stubs/wp-cli-stubsindirect
Packagistphpcompatibility/phpcompatibility-wpindirect
Packagistphpunit/phpunitindirect
Packagistsquizlabs/php_codesnifferindirect
Packagistszepeviktor/phpstan-wordpressindirect
Packagistwp-coding-standards/wpcsindirect
Packagistyoast/wp-test-utilsindirect
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 statisticsPackagist.