It includes tests, a readable package description, a declared MIT license, and a small dependency surface. The source has had no commits or releases since April 2017, and it provides no security policy, so future maintenance and vulnerability handling are uncertain.
55%
Total Score
50
100
86
50
The package has had four releases, all concentrated in April 2017, with no release in roughly nine years. That long silence is a meaningful maintenance concern, though it does not show that the package is unusable.
There were zero commits and zero active maintainers in the last three months, consistent with the last repository push in April 2017. This is the strongest evidence of abandonment risk in the collected signals.
Composer build tooling is present, but no security-scanning tooling was detected. That is a transparency and maintenance-hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. For a library intended to be integrated into applications, this modestly lowers maintenance transparency.
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.