Repository tests, release notes, and organization backing add useful context. No security policy is published, while the registry lists one publisher despite the organization ownership.
60%
Total Score
67
100
100
50
A post-autoload-dump script runs during installation. This is a relevant execution-time surface, but no provided evidence shows that it is unsafe.
Only one registry publisher is listed, which limits publishing redundancy, but the repository is owned by an organization, making a short registry list less concerning.
There were zero commits and zero active maintainers in the last three months. The recent release and June push provide some recency, but the current pause still raises maintenance risk.
No repository security policy was found, leaving disclosure and response expectations undocumented.
All 12 analyzed action references are unpinned, and three workflows grant top-level write permissions. The high-confidence bot-conditions finding in a pull_request_target workflow adds workflow hygiene risk, although no untrusted checkout or script-injection sink was found.
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.