42%
Total Score
unhealthy
No releases since April 2022 and a one-person, inactive project make abandonment the main concern.
The package has had only two releases, both in April 2022, with no releases in the last four years. This is strong evidence of abandonment risk for a dependency despite the stable version.
Only one registry maintainer is listed, and the project is backed by an individual repository owner rather than an organization. That leaves limited visible maintainer capacity if the sole maintainer stops working on it.
There were no new issues or pull requests and no merged pull requests in the last month. Combined with the old last push and release history, this supports a meaningful concern about inactivity.
The repository has zero stars and zero forks, with one watcher. Popularity is not required for a healthy small package, but these counters provide no supporting evidence of an active user or contributor community.
The project uses Composer for builds, which fits the Packagist ecosystem, but no security-scanning tooling was detected. The missing scanner is a hygiene gap rather than evidence that the package is unsafe.
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.