Usable with caveats: the package has a clear MIT license, tests, a useful README, and no deprecation or dangerous workflow findings. Adoption carries maintenance risk because it has only two releases and no commits in the last three months, while repository security hygiene is incomplete.
62%
Total Score
63
100
94
80
A single registry maintainer creates some bus-factor risk, although the linked repository is user-owned and the small project scope makes this less concerning than it would be for a large ecosystem package.
The registry namespace is backed by an individual repository owner rather than an organization, so the single-maintainer and low-activity concerns are not compensated by visible organizational backing.
Only two releases were published, both clustered on August 14, 2025, with no releases in the last 12 months; this is a meaningful maturity and maintenance concern for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, indicating that maintenance may have stalled despite the repository remaining unarchived.
No security policy is present, leaving vulnerability-reporting expectations undocumented for a package intended for application integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^10.0|^11.0|^12.0 | — | — |
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.