Healthy and actively maintained, with clear packaging and frequent releases. The main caveat is that all recent repository work comes from one contributor, alongside limited security-policy and workflow-permission hardening.
78%
Total Score
75
100
100
63
One workflow uses pull_request_target, which can require careful handling because it runs with elevated trust in pull-request contexts. No untrusted checkout or script-injection findings were detected, so this is a limited workflow concern rather than a severe signal.
One contributor made all 8 commits in the last 3 months, leaving a low operational bus factor. The active release history partly offsets this, but succession risk remains.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. Other evidence shows active maintenance, but it does not replace a disclosure process.
Four of five workflows lack top-level permissions declarations, and one workflow declares top-level write access. This is weaker least-privilege hygiene, although no untrusted checkout or script-injection workflow was found.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0|^12.0|^13.0 | — | — |
guzzlehttp/guzzle Version ^7.4 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
spatie/array-to-xml Version ^3.1 | — | — |
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.