The package has had no release or repository activity for nearly five years, with no active contributors and only one registry maintainer. It remains licensed, documented, tested, and not deprecated, but its stale maintenance makes this a risky dependency.
45%
Total Score
33
100
83
67
The latest release was published nearly five years ago, and there have been no releases in the last 12 months. This is strong evidence of an inactive release process for a Laravel integration package.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance between releases.
Only one account has registry publish access. The linked repository is user-owned rather than organization-backed, so there is little visible maintainer redundancy if that person stops maintaining the package.
The registry namespace and repository owner match, and the owner is a user account. This supports ownership consistency but offers no organizational backing to compensate for the thin maintainer base.
The repository has zero stars, forks, and watchers. Popularity is supporting evidence rather than decisive proof, but here it provides no compensating sign of community adoption or review.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^6.0 || ^7.0 || ^8.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.