The package is clearly licensed, documented, and tested in its source repository, with focused runtime dependencies. Its maintenance history is too short to establish staying power, and the automation setup needs tightening before relying on it broadly.
62%
Total Score
88
100
94
63
A post-autoload-dump install-time script is present, adding execution during installation. This is common Composer package behavior but still increases installation complexity compared with a package without lifecycle hooks.
The package is only 0 days old with three releases published within a short period, so there is not enough history to demonstrate sustained maintenance or stability.
There were no commits or active maintainers in the last three months, although the repository was only created or updated very recently. The current activity is therefore encouraging but not yet a sustained maintenance record.
No security policy was found in the repository. This is a transparency gap, though its impact is limited for a small package with very little operating history.
All five workflows were analyzed, but all 12 action references are unpinned. The audit also found a high-confidence bot-conditions issue in the Dependabot auto-merge workflow; the pull_request_target trigger has no untrusted checkout or script-injection sink, so this is a hygiene concern rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.92 | — | — |
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.