The project has a clear README, tests, changelog, and release notes. Maintenance is concentrated in one contributor, while workflow permissions and unpinned actions add avoidable upkeep and supply-chain exposure.
61%
Total Score
50
100
100
50
A post-autoload-dump install lifecycle script is present. This is an execution-time consideration, but the signal alone does not show unusual or unsafe behavior.
One contributor made all two commits in the last three months. This creates a clear continuity risk, and the repository is user-owned rather than organization-backed.
Only two commits were recorded in the last three months. That is some recent activity, but it is a thin maintenance pace for a package consumers may depend on.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the absence is a hygiene concern rather than evidence of abandonment.
All 12 action references are unpinned, and three workflows grant top-level write permissions. The audit also found a high-confidence bot-conditions issue in the Dependabot auto-merge workflow; no untrusted checkout or script injection was found, so this remains a meaningful caution rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0||^11.0||^12.0||^13.0 | — | — |
illuminate/contracts Version ^10.0||^11.0||^12.0||^13.0 | — | — |
barryvdh/laravel-dompdf Version ^3.1 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.