Regular releases, release notes, tests, and security scanning provide useful evidence of an active project. A single maintainer and no security policy add modest transparency risk; pin workflow actions before relying on automated releases.
68%
Total Score
50
100
50
One registry publisher is a modest continuity risk, though the linked repository is maintained by the same individual and recent release activity provides some compensation.
There were no commits from any active maintainer during the last three months, which is a meaningful maintenance concern despite the recent release and repository push.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
All 12 analyzed action references are unpinned, and two of four workflows grant top-level write permissions; the audit found no untrusted checkout, script injection, or high-severity issue, so this is workflow hygiene risk rather than a severe finding.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.9 | — | — |
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.