Usable with caveats: the release is well documented, tested, licensed, and not deprecated, but maintenance appears thin with no commits in the last three months and only one registry maintainer. Review the project before adopting it for a long-lived or security-sensitive integration.
68%
Total Score
50
100
89
80
Only one account has registry publish access. That does not prove the project lacks contributors, but it creates a single-point publishing and maintenance risk.
The package is backed by a personal-user repository rather than an organization, so the single registry maintainer is not offset by organizational ownership.
The package has existed for about 3 years 8 months with seven releases, but only one release in the last 12 months and a median interval of about 282 days indicate a slow maintenance cadence.
The repository recorded zero commits and zero active maintainers during the last three months. Although the March 30 release is recent, the absence of subsequent activity weakens confidence in ongoing maintenance.
The project uses Make and Composer for builds, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the release is unsafe.
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.