The prerelease label and absent security policy add uncertainty, while the package includes a license, README, and repository tests. Its release and commit activity has effectively stopped, making long-term support a significant concern.
42%
Total Score
33
100
71
83
The package has 88 releases but none in the last 12 months, and its latest release was published nearly five years ago. This strongly increases abandonment risk despite the historically active release count.
There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this is direct evidence that current maintenance has stopped.
The registry and repository are owned by the same individual account, so the source ownership is consistent. Individual ownership provides less visible organizational continuity than organization backing, but it is not itself a health failure.
There were no new or closed issues or pull requests in the last month, and nine pull requests remain open. This suggests limited current project responsiveness, although the activity measure is incomplete because open issue count is unknown.
The repository uses Composer for builds, providing basic build structure, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not a standalone adoption blocker.
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.