The package has a substantial README, repository tests, an MIT license, and Composer plus Dependabot tooling. A single release, no commits in three months, and 12 unpinned workflow actions leave limited evidence of sustained support.
58%
Total Score
50
100
94
50
Only one account has registry publish access, and the repository is user-owned rather than organization-backed. A single maintainer increases continuity risk for a package with little release history.
The registry namespace and repository are owned by the same individual, so the source linkage is coherent. However, the user-owned project provides less organizational continuity than an established team would.
This is the only release, published 287 days ago, with no additional releases in the last 12 months. The short history limits evidence of ongoing maintenance and release reliability.
There were zero commits and zero active maintainers in the last three months. This is direct evidence of currently inactive development for a package with only one release.
The repository has no security policy. For a Laravel library this is a transparency and reporting gap, although it is not by itself evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0||^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.