The project is young and has made no commits in the last three months, with no active contributors. Its clear README, MIT licensing, matching repository, and lack of install scripts support adoption, but security documentation is absent.
58%
Total Score
25
100
83
75
There were zero commits and zero active maintainers in the last three months, a concrete sign that maintenance may have stalled after the initial release burst.
The package and repository are owned by the same individual account. That is coherent ownership, but it indicates a single-person project rather than organizational backing.
The package is only 157 days old and all four releases occurred within four days, showing an early burst without enough history to establish durable maintenance.
The repository has zero stars, forks, and watchers. This is weak supporting evidence rather than a verdict, but it provides no external maturity signal for a young package.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^11.0|^12.0|^13.0 | — | — |
illuminate/console Version ^11.0|^12.0|^13.0 | — | — |
illuminate/routing Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/filesystem Version ^11.0|^12.0|^13.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.