The MIT license, clear README, repository tests, and release notes make integration straightforward. A single maintainer and tiny community leave little backup when maintenance stalls. Workflow permissions and unpinned actions add avoidable upkeep risk.
55%
Total Score
38
100
89
63
There have been no commits and no active maintainers in the last three months. Combined with no releases in the last 12 months, this raises a substantial staleness risk.
A post-autoload-dump install script is present. This is a normal Composer package hook, but it adds install-time behavior that should be understood before adoption.
Only one registry maintainer is listed, leaving limited publishing redundancy. Because the repository owner is also an individual, there is no organization backing shown to offset that concentration.
The package and repository are owned by the same individual account, with no organization backing shown. This is consistent ownership, but it provides limited continuity if the maintainer becomes unavailable.
The package has had no releases in the last 12 months, despite four releases overall and a short earlier median interval. This is a meaningful maintenance concern for a Laravel integration package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/auth Version ^10.0|^11.0 | — | — |
illuminate/support Version ^10.0|^11.0 | — | — |
illuminate/database Version ^10.0|^11.0 | — | — |
illuminate/contracts Version ^10.0|^11.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.