govigilant/laravel-healthchecks
Tests, release notes, clear documentation, licensing, and organizational backing provide a solid foundation. Its short history, no commits in the last three months, and unpinned workflow actions leave meaningful maintenance and build-integrity concerns.
67%
Total Score
75
100
88
83
Health Score Breakdown
The package is about 10 months old with three releases, all within the last 12 months, and a median interval of about 54 days. This shows real release activity but limited maturity.
The repository recorded zero commits and zero active maintainers in the last three months. With the latest release about six months ago, this is a meaningful sign of slowed maintenance, despite earlier releases.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene limitation rather than evidence that the package is unsafe or abandoned.
All three workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all six action references are unpinned, leaving builds exposed to moving action versions.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Vincent Bean |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^12.0|^13.0 | — | — |
govigilant/vigilant-healthchecks-base Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 months ago
- Created
- 9 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.