The package is small and easy to inspect, with tests, a matching repository, an MIT license, and only two runtime dependencies. Its maintenance has effectively stopped since December 2018, and the repository has no security policy or scanning, making long-term dependency risk substantial.
43%
Total Score
0
100
75
75
This package has had only one release, on December 24, 2018, with no releases in the last 12 months. That indicates prolonged abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, with its last push in December 2018. This confirms that the release-history gap reflects stopped development rather than only an infrequent registry cadence.
The repository has zero stars, forks, and watchers, providing no community evidence to compensate for the absence of maintenance activity. Popularity is supporting evidence rather than the primary concern.
Composer build tooling is present, but the repository has no security-scanning tools. That is a modest transparency and maintenance gap, especially for a package with no recent activity.
The repository has no security policy. This weakens vulnerability-reporting transparency, although it is secondary to the much stronger evidence of long-term inactivity.
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.