Documentation, repository tests, release notes, and a clear MIT license support straightforward adoption. However, the project has had no commits or releases for over four years, with no security policy and low community activity.
58%
Total Score
25
100
72
67
The package has made no release in over four years, and it had no releases in the last 12 months. This is a substantial maintenance concern for a Laravel integration package.
There were 0 commits and 0 active maintainers in the last three months, consistent with the package's long release gap and increasing abandonment risk.
The registry namespace and repository are owned by the same individual account, providing consistent ownership but no organizational backing to compensate for the inactive project.
The repository has 2 stars, 0 forks, and 1 watcher. Low popularity is supporting evidence rather than a verdict, but it provides little indication of an active user or contributor community.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap, not a standalone reason to reject the release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.0|^9.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.