The package is well documented, tested, licensed, and clearly tied to its source repository. Its small release history and no commits for about 16 months make future maintenance uncertain, while the repository lacks security scanning and a security policy.
60%
Total Score
88
100
89
83
Only two releases arrived on the same day, and there have been no releases in about 16 months. This leaves limited evidence of sustained maintenance for a package developers may depend on.
There were zero commits and zero active maintainers in the last three months, consistent with roughly 16 months without a push. This is the main abandonment concern.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than a standalone severe risk.
The repository has no security policy. That weakens vulnerability-reporting transparency, though the tested and documented package structure provides some compensating evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0 | — | — |
illuminate/validation Version ^10.0|^11.0|^12.0 | — | — |
illuminate/translation Version ^10.0|^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.