The repository has tests, a changelog, a clear license, and organization backing. Its workflow audit found no dangerous patterns, but the build references two unpinned actions and the project has no security policy or automated security scanning.
58%
Total Score
75
83
75
The package has only three releases, all within about eight days, and none in the last 12 months despite being about 386 days old. That short history and prolonged release gap raise maintenance risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly one-year release gap. This is a meaningful abandonment concern for a young package.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning reduces maintenance assurance alongside the repository's limited recent activity.
The linked repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a transparency gap, though it is not by itself evidence that the package is unsafe.
The single workflow was fully analyzed with no dangerous audit findings or untrusted checkouts, but both referenced actions are unpinned. That weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/mail Version ^10.0|^11.0|^12.0 | — | — |
guzzlehttp/guzzle Version * | — | — |
illuminate/events Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.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.