The package has a clear README, tests, changelog, MIT license, and only one runtime dependency. Its last release and repository update were nearly five years ago, making abandonment the main concern despite the stable release history.
42%
Total Score
100
71
50
The package has had no release in nearly five years, with zero releases in the last 12 months. The 19-release history shows an active initial period but does not offset the prolonged inactivity.
Composer is used as the build tool, showing basic project tooling, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not a standalone adoption blocker.
The repository is not archived, which preserves a path for future maintenance, but its last push was nearly five years ago and confirms the long period without visible updates.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more because the project has shown no recent maintenance activity.
No GitHub Actions workflows were present, so there were no workflow risks to flag, but there is also no CI evidence from this signal. With no workflows to analyze, this is neutral rather than a clean bill of health.
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.