The stable release, clear licensing, documentation, and matching repository provide useful reassurance. Maintenance has paused recently, while workflow permissions, unpinned actions, and a high-confidence bot check reduce confidence in ongoing upkeep.
68%
Total Score
50
100
100
50
A post-autoload-dump install-time script is configured. This is a modest supply-chain and installation-complexity concern, although only one script is reported and its behavior is not shown here.
One registry maintainer is listed, and the repository is owned by the corresponding individual account. This creates a thin maintainer base and limited visible succession capacity.
There were 0 commits and 0 active maintainers in the last 3 months. That is a meaningful maintenance warning despite the recent release and repository push evidence.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it does not by itself show abandonment.
All 10 analyzed action uses are unpinned, two workflows grant top-level write access, and a high-confidence bot-conditions finding affects the Dependabot auto-merge workflow. The pull_request_target trigger has no untrusted checkout or script-injection sink, so this is workflow weakness rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0||^11.0||^12.0||^13.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.