Risky to adopt for a new project: the package has not released an update since January 2018 and its repository has had no recent commits. It is not deprecated or archived, and it has a clear license and usable README, but the long-term abandonment risk is substantial.
42%
Total Score
25
72
75
The latest release was in January 2018, more than 8 years ago, with no releases in the last 12 months and only 5 releases overall. This is strong evidence of abandonment risk despite the package remaining published.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history and indicating that fixes and compatibility work are unlikely.
The registry namespace and repository owner match, showing that the package is backed by the linked personal repository rather than an unrelated project. The owner type is a user account, so there is limited evidence of organizational continuity.
The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is not decisive by itself, but this provides little community evidence to compensate for the lack of maintenance.
Composer is used as a build tool, but no security scanning tooling is present. This is a transparency and maintenance gap, though the absence of tooling is less severe than the prolonged 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.