Clear documentation, licensing, and organization backing reduce adoption friction. The project shows little evidence of an established maintenance process, so future fixes and compatibility updates are uncertain.
55%
Total Score
75
100
88
75
The package has 11 releases in the last 12 months, but the median interval is only about 2 hours, indicating a concentrated burst rather than a steady release cadence. That activity is partly reassuring but does not offset the recent lack of commits.
The repository recorded 0 commits and 0 active maintainers in the last three months, despite the package having recent releases. This is the strongest evidence of possible maintenance slowdown.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance-process gap, not a severe risk by itself.
No repository security policy was found, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though the package remains licensed and its source repository is available.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^11.0|^12.0 | — | — |
illuminate/routing Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
illuminate/filesystem 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.