The package is clearly licensed, documented, and tested in the source repository, with no install-time scripts or deprecation. Its small scope and organization backing help offset the limited security tooling and workflow pinning.
72%
Total Score
80
100
88
75
Only one registry account has publish access. That is a resilience concern, but the repository is owned by an organization, which provides some backing beyond the registry access list.
The package has 42 releases over about 3 years, but only 1 release in the last 12 months despite a historical median interval of about 11 days. This indicates a meaningful slowdown, though recent repository activity provides some compensation.
All 8 recent commits came from one contributor, creating a high single-person dependency. Organization ownership partly compensates because maintenance can potentially be handed off.
Composer is used for builds, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy. That makes vulnerability reporting and response expectations less clear, although it does not by itself indicate abandonment.
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.