Healthy and suitable to depend on. It has a long release history, frequent recent releases, current maintenance, tests, documentation, and a clean package-to-repository match; the main caveats are reliance on one active maintainer and limited repository security controls.
88%
Total Score
70
100
94
75
Only one registry account has publishing access. That is a concentration concern for publishing continuity, though the repository's sustained release activity provides compensating evidence of active ownership.
The registry namespace and repository are owned by the same individual, which establishes clear ownership but does not provide organizational maintenance redundancy.
One contributor made all four commits in the last three months, so maintenance depends heavily on a single person. The project is user-backed rather than organization-owned, making this a genuine continuity concern.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and process gap, not evidence that the package is unsafe by itself.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cakephp/cakephp Version ^5.1.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.