The project includes tests, a clear MIT license, and a matching organization-backed repository. Its sparse release history and no commits in the last three months limit confidence in ongoing maintenance; workflow hygiene also needs attention.
68%
Total Score
75
88
75
Only three releases have been published since June 2022, with a median interval of about 665 days, although two releases arrived in the last 12 months and the latest was recent.
There were no commits and no active maintainers in the last three months. The recent release provides some compensating evidence, but the lack of ongoing commit activity still lowers maintenance confidence.
Composer build tooling is present, but no repository security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear.
All six workflow action references are unpinned, and the audit found one high-confidence unsound condition; the three cache-poisoning findings are low confidence and therefore hygiene concerns only. The workflow audit itself is complete.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.