Tests, documentation, and a clean package install reduce day-to-day adoption friction. The organization-backed project has a narrow recent contributor base, while workflow permissions and action pinning need tightening.
80%
Total Score
83
100
94
67
One contributor made 13 of 14 recent commits, so maintenance is concentrated. The organization-owned repository provides some handoff capacity, but the recent activity still depends heavily on one person.
Composer is used for builds, but no security-scanning tooling was detected. The missing scanner is a modest transparency gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a maintenance and transparency gap, though the active project provides some compensation.
The single workflow was fully analyzed with no reported high-confidence findings or untrusted sinks, but all three action references are unpinned and the workflow grants top-level write permissions. These are workflow hygiene concerns, not severe risks on their own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/view Version ^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
matthiasmullie/minify Version ^1.3 | — | — |
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.