Tests, release notes, a matching repository, and an MIT license provide useful transparency. The small maintainer base and workflow pinning reduce resilience and reproducibility.
72%
Total Score
67
100
94
50
The repository is owned by an individual user rather than an organization, so the concentrated contributor activity is not visibly offset by broader organizational backing.
The package is 600 days old with four releases and two releases in the last 12 months, but the median interval is about 184 days, indicating a measured rather than rapid cadence.
One contributor made all seven commits in the last three months, leaving maintenance highly concentrated and creating a meaningful continuity risk.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
The single workflow was fully analyzed with no untrusted checkout, script injection, or audit findings, and it does not grant top-level write access. However, all six referenced actions are unpinned, weakening build reproducibility, while the absence of a top-level permissions block is ordinary and not a concern on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
cakephp/cakephp Version ^5.0.1 | — | — |
arodu/cakephp-utility-kit Version ^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.