A README, tests, release notes, and no runtime dependencies make the package straightforward to inspect and integrate. The repository-to-package naming mismatch and absent security policy further reduce confidence in long-term stewardship.
38%
Total Score
0
100
63
75
Only two releases were published, both in April 2016, with no release in roughly 10 years. This is strong evidence of abandonment for a library consumers may need maintained over time.
There were no commits and no active maintainers in the last three months, consistent with the long gap since the last release and indicating no current maintenance capacity.
The repository name does not match the package name and its README does not mention this package, so the source may not clearly belong to the published package. A monorepo explanation is not shown by the provided evidence.
The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy small package, but these figures provide no supporting evidence of active community oversight.
Composer is used for the build, but no security scanning tools are present. This is a secondary hygiene gap rather than a standalone reason to reject the package.
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.