The small codebase includes tests, a clear MIT license, and no install-time scripts or runtime dependencies. Maintenance evidence is thin, with no commits for over eight months, only two releases, one registry maintainer, and no security policy or scanning.
58%
Total Score
50
100
79
75
Only one registry account has publishing access, and project_backing identifies an individual repository owner rather than an organization. This leaves limited visible maintainer redundancy.
The package contains tests and the repository also has tests, but no README is published for this small library. That weakens consumer guidance, while the missing changelog is normal packaging practice.
The package has only two releases, with the latest published over eight months ago. Its initial release spacing was about seven days, but the short history provides limited evidence of sustained maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the release history, this is meaningful evidence of currently inactive maintenance.
Composer is used as the build tool, but no security scanning tool is configured. The missing scanner is a hygiene limitation, not evidence that the package is unsafe by itself.
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.