The stable v1.0.1 release, tiny dependency surface, clear README, and intact source repository make integration straightforward. Maintenance visibility is limited because both releases and repository activity stopped more than eight years ago, with no security policy.
58%
Total Score
67
100
88
75
Only two releases exist, with the latest published more than eight years ago and none in the last 12 months. The small, stable package scope partly offsets the long period without updates, but maintenance is uncertain.
There were no commits or active maintainers in the last three months, consistent with a project that has been inactive for more than eight years. The repository is still present, but this is a meaningful abandonment concern.
There has been no issue or pull request activity in the last month, and one issue remains open. This reinforces limited current maintenance visibility, though the small project may require little ongoing support.
Composer build tooling is present, but no security-scanning tooling was detected. For this small package that is a modest transparency gap rather than a severe risk.
The repository has no security policy. That limits guidance for reporting vulnerabilities, although the package's small scope reduces the practical impact.
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.