The package has a clear README, a coherent small artifact, a declared license, and organization backing. Maintenance evidence is now stale, with no recent commits, issues, or releases, while missing security tooling leaves a smaller transparency gap.
62%
Total Score
67
86
50
The package has 13 releases and a healthy historical median interval of about 17 days, but it has had no release in the last 12 months. That prolonged pause lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release pause. This is meaningful abandonment risk for a dependency that may need updates.
There were no new or closed issues and no merged pull requests in the last month, with two issues still open. This provides no evidence of current issue handling and reinforces the maintenance concern.
Composer is used as the build tool, which fits the package, but no security-scanning tools were detected. That is a modest transparency and maintenance gap rather than a severe risk on its own.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. For a small package this is a minor transparency gap.
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.