It has a clear MIT license, tests, a README, and no install-time scripts. The small project has no security policy or scanning, leaving limited evidence about ongoing maintenance and issue response.
53%
Total Score
50
79
75
One registry maintainer is consistent with a small individual project, but it provides little redundancy if that maintainer becomes unavailable. The linked repository also shows no recent active maintainers.
The package has made only one release, on March 31, 2022, with no releases in the last 12 months. This is strong evidence of limited maintenance for a package intended as a Laravel development dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old release history, this increases abandonment risk, though the repository is not archived.
Composer build tooling is present, but no security scanning tools were detected. For a package that runs as part of a Laravel project, this is a modest transparency and maintenance gap.
The repository has no security policy. This does not make the package unsafe by itself, but it gives users no documented route for reporting vulnerabilities or understanding disclosure practices.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.19|^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.