The project has a complete consumer-facing package, documented releases, and a repository with tests and a security policy. Workflow references are all unpinned and the release workflow has high-confidence template-injection findings, which warrants extra caution around its build process.
79%
Total Score
100
100
94
100
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest process gap for a dependency project.
All four workflows were analyzed, but all nine action references are unpinned, and the release workflow contains five high-confidence template-injection findings. The findings are workflow hygiene concerns rather than the stronger trigger-and-sink danger described by the audit rules.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^2.72.2|^3.10 | — | — |
illuminate/view Version ^12.0|^13.0 | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/contracts Version ^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.