Additional Checks for Laravel Health (Spatie)
80%
Total Score
healthy
Healthy: regular releases and an active repository outweigh the single-maintainer risk.
The repository is owned by an individual user rather than an organization, so the single-contributor concentration is more consequential and is not supported by organizational handoff capacity.
All three recent commits came from one contributor, leaving maintenance dependent on a single active person. The package's release activity partly offsets this, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tool is reported. The missing scanning is a transparency gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a moderate transparency gap, not an abandonment signal.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-health Version ^1.39 | — | — |
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.