The README, changelog, MIT license, and matching repository make the package easy to inspect and adopt. Its single-maintainer project has had no releases or commits for about two years, and no security scanning or security policy is configured.
58%
Total Score
50
100
81
83
The package has had five releases, all concentrated around its first two days, with no release in about two years. That strongly lowers confidence in ongoing maintenance for a dependency.
One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing redundancy when combined with the absence of recent activity.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release pause. The package may be stable, but there is little evidence of current maintenance capacity.
Composer is used for the build, but no security scanning tool is configured. The missing scanning reduces supply-chain hygiene, though it does not by itself make the package unfit.
The repository has no security policy, which makes reporting and handling vulnerabilities less transparent. This is a hygiene and maintenance concern rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^5.0|^6.0|^7.0|^8.0|^9.0|^10.0|^11.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.