The package has clear release notes, a matching repository, and dependency-update tooling. Its single registry maintainer and missing security policy leave less operational depth if maintenance slows.
58%
Total Score
63
100
100
50
Only one account has registry publish access. The matching repository and regular release history provide some compensation, but the publishing base remains narrow.
The repository and registry are owned by the same individual account, so the package has direct ownership alignment but no demonstrated organizational backing.
The repository recorded zero commits and zero active maintainers in the last three months. A recent push and three merged pull requests show some activity, but the current commit pause raises maintenance risk.
No repository security policy was found. This is a transparency and vulnerability-reporting gap, though it does not by itself show that the package is unsafe.
All six workflows were analyzed with no untrusted checkout or script-injection findings and all 21 action references pinned. However, the audit found one high-confidence template-injection issue in bump-docs-version.yml; template injection is a workflow hygiene concern unless corroborated by an exploitable trigger or sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^12.0 || ^13.0 | — | — |
intervention/image-laravel Version ^4.0.0 | — | — |
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.