It has tests, release notes, a clear license, and no install-time scripts. One maintainer, no security policy, and unpinned workflow images leave modest operational risk.
77%
Total Score
67
100
93
75
The package and repository are both owned by the same individual account. This confirms source alignment but provides no organizational handoff capacity to offset the concentrated maintainer base.
All 4 recent commits came from one contributor, giving the project a concentrated maintenance base. Because the repository owner is an individual rather than an organization, this remains a meaningful continuity concern.
Composer build tooling is present, but no security scanning tools were detected. The package still has active releases and repository tests, so this is a modest transparency gap rather than a severe risk.
The repository has no security policy. That does not show a security defect, but it reduces transparency about how dependency and vulnerability reports are handled.
Both workflows were analyzed without failures, but all 12 action references are unpinned and a high-confidence finding identifies an unpinned container image; one workflow also grants top-level write permissions. These are workflow supply-chain hygiene concerns, not evidence that the package itself is unsafe.
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.