Tests, a clear MIT license, a small dependency surface, and organization ownership provide useful support. The workflow uses three unpinned actions and the repository has no security policy, leaving maintenance and build hygiene concerns.
58%
Total Score
75
100
88
75
Only three releases have been published, with the latest in January 2023 and none in the last 12 months. This indicates a long period without release maintenance, though the stable 2.0.0 line may reduce the need for frequent releases.
There were no commits and no active maintainers in the last three months. This is a meaningful maintenance concern, even though the repository was pushed more recently than the last release.
The project uses Make and Composer for build tasks, but no security scanning tool was detected. That weakens automated maintenance hygiene without showing a direct dependency risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The single workflow was fully analyzed with no untrusted checkout or script-injection findings, but all three referenced actions are unpinned. That creates avoidable build reproducibility and action-update risk.
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.