Monitor the health of a Laravel application
42%
Total Score
unhealthy
Risky: the only release was over four years ago and repository activity has stopped.
This is the package's only release, published over four years ago, with no releases in the last 12 months. That strongly suggests abandonment risk despite the repository still being available.
The repository had zero commits and zero active maintainers in the last three months. This is the clearest evidence that maintenance has stopped.
Thirteen runtime dependencies create meaningful maintenance surface for a Laravel package, though the listed dependencies are consistent with its framework, database, notification, and health-check features.
Only one registry account has publish access, which is a resilience concern. The organization-owned repository provides some backing, so this is not by itself evidence of abandonment.
There were no new or closed issues or pull requests in the last month, and no pull requests were open. Combined with the old release, this supports a low-maintenance assessment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/enum Version ^3.11 | — | — |
spatie/regex Version ^3.1 | — | — |
symfony/process Version ^5.4|^6.0 | — | — |
guzzlehttp/guzzle Version ^6.5|^7.4 | — | — |
illuminate/console Version ^8.75 | — | — |
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.