Clear documentation, repository tests, and a minimal dependency footprint reduce adoption friction. Maintenance is concentrated in one contributor, and workflow references are unpinned, so future continuity and build reproducibility deserve attention.
78%
Total Score
70
100
94
83
Only one registry account has publish access. This is a continuity concern, although the repository shows recent release and commit activity from that maintainer.
The repository is owned by an individual user rather than an organization, so the single-contributor concentration is not visibly offset by organizational handoff capacity.
All 20 recent commits came from one contributor, giving the project a concentrated maintenance base and increasing continuity risk.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy, leaving reporting and response expectations undocumented for users and researchers.
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.