The repository includes tests, a changelog, a matching README, and a clear MIT license. Registry releases stopped nearly four years ago, recent commit activity is absent, and all workflow actions are unpinned; no security policy is present.
56%
Total Score
50
75
50
The package has had no release in nearly four years, with 0 releases in the last 12 months. That materially raises maintenance and abandonment concerns despite 34 historical releases.
There were 0 commits and 0 active maintainers in the last three months. This is direct evidence of currently weak maintenance activity, even though the repository is not archived.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest hygiene gap rather than evidence that the package is unsafe by itself.
The repository has no security policy, reducing transparency for vulnerability reporting and maintenance expectations. The otherwise healthy repository structure does not compensate for this documentation gap.
The release is marked stable rather than prerelease, which supports predictable adoption, but the registry reports v1.1.11 as latest while the assessed version is v2.0.3, reducing confidence in the version metadata.
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.