The repository has no security policy or scanning, and its README does not name the package. Dependencies are modest and licensing is clear, but there is little evidence of ongoing support.
55%
Total Score
50
79
75
All three releases arrived within about one day, followed by roughly nine months without a new release. This suggests an immature project with no demonstrated release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. That is meaningful abandonment risk for a package released only once in a short burst.
The repository name matches the package, but the README does not mention the package name. That weakens confidence that the published artifact and source are clearly connected.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces supply-chain hygiene evidence without making the package unfit by itself.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/view Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.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.