Its documentation, licensing, release notes, and repository match are reassuring. The small project has little adoption, no recent commit activity, and workflow safeguards need attention, so pinning this release carries meaningful maintenance risk.
47%
Total Score
50
100
88
33
The audit found a high-confidence, high-severity bot-condition issue, all 12 action references are unpinned, and three workflows grant top-level write access. There is no untrusted checkout or script injection, but the automation still has materially weak safeguards.
The package uses a post-autoload-dump install-time script. That is a meaningful execution surface for consumers, although this signal does not show that the script is unsafe.
One registry maintainer is responsible for publishing the package, leaving limited publishing capacity. The repository is user-owned, so the short maintainer list is less easily explained by organization backing.
The package and repository are both owned by the same individual account, with no organization backing shown. This is consistent and transparent, but it confirms reliance on a single project owner.
Only two releases were published, both about 455 days ago, with no releases in the last 12 months. This leaves the package's ongoing maintenance uncertain despite its stable v1.0.1 version.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0||^11.0||^12.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.