The package has a clear README, a stable release, and only one runtime dependency. Its source repository matches the package, the release has notes, and installation has no lifecycle scripts, but ongoing maintenance appears limited.
54%
Total Score
50
100
88
75
The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This offers limited backing evidence and does not compensate for the inactive history.
Only two releases were published, both in early 2022, with no release in roughly four years. This materially raises abandonment risk despite the package being stable.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with no meaningful development since March 2022. This is the strongest maintenance concern for a dependency.
Composer is used for the build, but no security scanning tooling is present. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is not by itself evidence of abandonment or malicious behavior.
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.