The MIT license, matching repository, tests, and release notes support a transparent project. Its small release history and unpinned CI actions add modest maintenance and build-reproducibility concerns.
68%
Total Score
75
88
50
The package has eight releases over about 3 years and 8 months, but only one release in the last 12 months with a median interval of about 6 months. This indicates a small, relatively slow release cadence rather than abandonment by itself.
There were zero commits and zero active maintainers in the past three months. Although the latest release was recent, the absence of recent source activity lowers confidence in ongoing maintenance.
The project uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented, creating a minor project-transparency gap.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or injection findings. However, both action references are unpinned, which weakens build reproducibility; the missing top-level permissions block is acceptable on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http 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.