All six workflow actions are unpinned, and the repository has no security policy or automated security scanning. Active organization-backed development, testing, licensing, and balanced contributors reduce the abandonment concern.
67%
Total Score
100
75
75
The latest registry release was about 2 years and 4 months ago, with no releases in the last 12 months. This is a meaningful adoption and maintenance concern despite recent repository activity.
Composer is used for builds, but no security-scanning tools were detected. This leaves a transparency and detection gap for a security-sensitive SDK.
The repository has no security policy, so its process for reporting and handling vulnerabilities is not documented.
The package remains on the 0.x line, so its API may still change and offers less stability than a mature major release. No recent prerelease churn partly offsets that concern.
Both workflows were analyzed successfully with no dangerous audit findings or untrusted-code sinks, but all 6 action references are unpinned. Unpinned actions weaken build reproducibility and supply-chain control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
shanecurran/phpecc Version ^0.0.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.