Its documentation, licensing, and release notes give consumers a clear integration path. The small project has no security policy, and its two workflow actions are unpinned, but recent publishing and an intact source repository reduce abandonment concerns.
78%
Total Score
100
100
89
67
A post-autoload-dump install script is present; this adds some installation-time behavior, but the signal gives no evidence that it is unsafe or unusually complex.
The repository has four stars and no forks or watchers, showing limited community adoption. For a small, focused package this is supporting caution rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and hygiene gap, without evidence of a failing build or known vulnerability.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not severe enough to make the release unfit on its own.
All workflows were analyzed with no injection, untrusted-checkout, or auditor findings, and no top-level write permissions. However, both action references are unpinned, which leaves the CI supply chain less reproducible.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-health Version ^1.30 | — | — |
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.