Clear documentation, tests, a small dependency surface, and a permissive license reduce adoption friction. The package has seen no development since November 2022, and the linked repository does not identify it in its README.
45%
Total Score
0
100
56
83
Only two releases were published, both on November 2, 2022, with no releases in the following years. This is strong evidence of abandonment risk for a dependency.
There were no commits and no active maintainers in the last three months, consistent with the long release hiatus. This materially increases abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although name differences can occur, the combined mismatch weakens confidence that the linked source clearly belongs to this release.
The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small utility, but it offers no supporting evidence of community maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
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.