Its MIT licensing, small dependency surface, and clear README reduce adoption friction. The organization-owned repository is intact, but ongoing support and security oversight are not evident.
42%
Total Score
50
100
78
83
The package has only two releases, both published in June 2018, with no releases in about eight years. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release hiatus. No provided activity signal compensates for this lack of recent maintenance.
The repository has zero stars, zero watchers, and one fork, indicating very limited visible adoption or community support. Popularity is supporting evidence only, but it reinforces the lack of maintenance capacity.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a transparency and hygiene concern for a package that has otherwise gone unmaintained.
The repository has no security policy, leaving no documented route for reporting vulnerabilities. This adds a security-maintenance gap alongside the stale project activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.