MIT licensing, clear documentation, and release notes make adoption easier. The organization-backed repository is active, but its sole recent contributor, missing security policy, and unpinned workflow actions reduce confidence.
67%
Total Score
100
100
88
75
The latest registry release is over two years old, with no releases in the last 12 months. Recent repository activity partly offsets the maintenance concern, but does not replace a current published release.
The project uses Composer and Make, but no security scanning tools were detected. That is a maintenance and transparency gap, though not evidence that the release is unsafe.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented.
Both workflows were analyzed cleanly with no detected dangerous sinks or audit findings, but all 12 action references are unpinned. That weakens build reproducibility and exposes the workflow to action-reference changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^8 || ^9 || ^10 || ^11 | — | — |
illuminate/support Version ^8 || ^9 || ^10 || ^11 | — | — |
illuminate/contracts Version ^8 || ^9 || ^10 || ^11 | — | — |
thecodingmachine/safe Version ^1 || ^2 | — | — |
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.