Clear documentation, release notes, repository tests, and a security policy support responsible use. The workflow uses read-only permissions but leaves both actions unpinned, weakening build reproducibility.
70%
Total Score
83
79
100
The package is only 52 days old, although it has already shipped 8 releases with a frequent cadence. This shows active early development but provides limited evidence of long-term maturity.
All 53 recent commits came from one contributor, creating a real continuity risk. Organization backing provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tool was detected. The repository's security policy partly offsets the transparency gap, but not the lack of automated scanning.
v0.4.0 is not a stable major release, so its API and generated output may still change substantially. It is not marked as a prerelease, which provides some compensation.
The workflow was fully analyzed, uses read-only permissions, and has no reported audit findings or untrusted execution paths. Both of its action references are unpinned, leaving a modest reproducibility and action-integrity concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/filesystem 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.