The small contributor base leaves some continuity risk, and the repository lacks a security policy and automated security scanning. Recent releases, repository tests, and established packaging practices provide useful balance.
82%
Total Score
75
100
94
83
The repository is owned by an individual rather than an organization, so the concentrated recent contribution pattern has less institutional backing to offset it.
Two contributors were active recently, but the top contributor made 80% of the 5 commits. The second active contributor partly reduces, but does not eliminate, continuity risk.
The project uses Make and Composer, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of unsafe code.
The repository has no security policy. That weakens the project's documented vulnerability-reporting process, though it does not by itself indicate abandonment.
All 3 workflows were analyzed with no audit findings or dangerous untrusted checkouts, and none grants top-level write access. However, all 9 action references are unpinned, leaving a reproducibility and action-integrity hygiene gap.
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.