The project has clear upgrade guidance, tests, and a recent release. Maintenance is concentrated in one contributor, and the repository has no security policy or scanning, so ongoing stewardship is a modest concern.
79%
Total Score
67
100
94
75
All six recent commits came from one contributor, giving the project a one-person recent bus factor. Organization ownership provides some handoff capacity, but no second active contributor is shown.
The repository recorded six commits in the last three months, showing recent activity. However, only one maintainer was active during that period, limiting the resilience of that activity.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning is a process gap, though it is not evidence of unsafe code by itself.
The repository has no security policy. For a Redis cache adapter this is a transparency and incident-reporting gap, but it is not severe enough to outweigh the active release history and repository backing.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/cache Version ^3.0 | — | — |
predis/predis Version ^2.0 || ^3.0 | — | — |
psr/simple-cache Version ^2.0 || ^3.0 | — | — |
cache/adapter-common Version ^3.0 | — | — |
cache/hierarchical-cache Version ^2.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.