The package is small, tested, MIT-licensed, and has a minimal dependency surface. Its very low adoption and lack of recent project activity make future fixes and support uncertain.
60%
Total Score
75
100
81
75
The package has had three releases, all in November 2020, with no release in nearly six years. That strongly limits evidence of ongoing maintenance, though a stable library may not need frequent releases.
There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive since November 2020. This is a meaningful abandonment risk even though the package is not archived.
The repository has zero stars and forks and only one watcher, showing very limited community adoption or external review. Popularity is supporting evidence rather than decisive proof, but it provides little confidence that problems will be noticed or fixed.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap and does not by itself indicate that the release is unsafe to depend on.
The repository has no security policy, leaving no documented route for reporting vulnerabilities. This is a transparency gap, but it is less severe than the clear maintenance concerns.
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.