The project has had no commits or releases for more than four years, with only one maintainer and no security scanning. A clear README, MIT license, release notes, and no install scripts provide useful transparency, but the maintenance gap remains substantial.
45%
Total Score
33
100
64
88
The latest release was in April 2022, and there have been no releases in the last 12 months. This long gap materially increases abandonment risk despite the earlier 16-day median release interval.
There were zero commits and zero active maintainers in the last three months, consistent with the multi-year release gap. This is strong evidence that maintenance has stopped.
Only one registry account has publish access. For this user-owned project, that is a thin publishing and continuity base, although registry access alone does not establish actual maintenance activity.
The repository is owned by an individual user rather than an organization, and the registry namespace differs from that owner. This provides no visible organizational continuity to compensate for the single-maintainer, inactive-project profile.
Composer is used as a build tool, but no security scanning tools were detected. The missing scanning is a hygiene weakness, though it is less severe for this small package than the lack of maintenance.
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.