The package has a long release history, a stable version, a clear README, repository tests, and release notes for this version. Maintenance is concentrated in one contributor, and no commits were recorded in the last three months.
72%
Total Score
50
100
94
100
Only one account has registry publishing access. That is a thin publishing base for a user-owned project and increases continuity risk if the sole maintainer stops releasing.
No commits or active maintainers were recorded in the last 3 months. The recent release partly offsets this, but the immediate development activity is quiet.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence of a defect.
The workflow uses read-only permissions and has no detected dangerous triggers, untrusted checkouts, or audit findings. However, all 4 of 4 action references are unpinned, weakening build reproducibility and update control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rancoud/security Version 4.0.3 | — | — |
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.