The small codebase has no tests or security scanning, and maintenance has gone quiet for over a year. Clear licensing, a matching repository, and no deprecation or install scripts reduce adoption risk.
58%
Total Score
38
100
78
75
There were zero commits and zero active maintainers in the last three months. Combined with no release in over a year, this materially raises abandonment risk.
One registry maintainer publishes the package. This is a thin publishing base and leaves limited redundancy if that person stops maintaining it.
A README explains installation and usage, but the package and repository have no tests or changelog. The missing tests reduce confidence in a library consumers integrate into applications.
The registry namespace and repository belong to the same individual account, providing direct ownership consistency but no organizational backing or maintainer redundancy.
There have been seven releases since September 2022, but none in the last 12 months; the latest release was over a year ago. This indicates a meaningful maintenance slowdown, though not abandonment by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^10|^11|^12 | — | — |
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.