The package is clearly documented, tested in the repository, and built with a clean, fully analyzed workflow. Its focused scope and low popularity are not concerning, but maintenance depends on one contributor and lacks a security policy.
73%
Total Score
67
100
88
83
The registry namespace and repository are owned by the same individual account. This is consistent ownership, but it does not provide organizational backing or redundancy.
The package has four releases over 696 days and one release in the last 12 months. This is a modest cadence and leaves some uncertainty about long-term maintenance, though the repository was pushed recently.
All three recent commits came from one contributor, so maintenance continuity depends entirely on that person. The repository owner is an individual rather than an organization, providing no shown handoff capacity.
Composer is used for builds, but no security-scanning tools were detected. The missing scanning layer is a modest transparency and maintenance gap.
The repository has no security policy, leaving users without a documented process for reporting vulnerabilities or understanding response expectations.
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.