Tests and release notes provide useful project evidence, and the repository is not archived or deprecated. The tiny audience and missing security safeguards make long-term support less certain.
58%
Total Score
50
79
75
No declared license or license file was found in the package or repository. That creates a real legal and adoption gap for downstream users.
The package has four releases but none in the last 12 months; its latest registry release was in November 2024, nearly two years ago. This materially raises maintenance risk despite a previously regular median release interval.
The repository recorded zero commits and zero active maintainers in the last three months. The repository was pushed more recently, but the current lack of commit activity still weakens evidence of active maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest supply-chain hygiene gap rather than a severe risk on its own.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency weakness, though it is not evidence of a vulnerability.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.48 | — | — |
illuminate/view Version ^10.48 | — | — |
spatie/ignition Version ^1.15 | — | — |
illuminate/config Version ^10.48 | — | — |
illuminate/contracts Version ^10.48 | — | — |
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.