It has a clear MIT license, a substantial README, tests, and release notes. The repository is not archived and has no deprecation warning, but maintenance evidence is thin after its first release. No security policy or scanning tooling is present.
62%
Total Score
33
81
75
There were zero commits and zero active maintainers in the past three months. For a package only about five months old with one release, this is thin evidence of ongoing maintenance.
The package and repository are owned by the same individual account, which is consistent with a small project. It does not provide the broader maintenance capacity that organizational backing might offer.
This is a young package, about 163 days old, with only one release and no established release cadence. That limits evidence of long-term maintenance, though it is consistent with a first public release.
There are no open issues or pull requests, but there was also no issue or pull-request activity in the past month. This provides little evidence of an active maintenance process.
Composer build tooling is present, but no security scanning tools were detected. The missing scanner is a hygiene gap rather than proof of unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/config Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/events Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/console Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^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.