A single registry maintainer and no security scanning reduce confidence in ongoing support. The MIT license, small dependency surface, matching repository, and documented setup are positives, but they do not offset the project’s inactivity.
38%
Total Score
50
100
72
83
The latest release was published in February 2020, with no releases in the last six years and only six releases overall. This is strong evidence of abandonment for a Laravel integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package’s long release hiatus. The repository is not archived, but it shows no current maintenance.
Only one registry account has publish access. The repository is organization-owned, so the short registry list is normal publishing hygiene rather than proof of a one-person project, but it still offers limited visible publishing redundancy.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no community signal to offset the inactivity.
Composer build tooling is present, but no security-scanning tools were detected. The build setup is reasonable, while the missing scanning provides little evidence of ongoing security maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5|~6 | — | — |
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.