Perform various self diagnosis tests on your Laravel application.
46%
Total Score
unhealthy
Risky: a single release has had no registry updates, with no recent commit activity to show ongoing maintenance.
This is the only release, published about 33 months ago, with no releases in the last 12 months. That prolonged lack of release activity materially raises abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old sole release, this supports a substantial maintenance concern.
The repository uses Composer build tooling, but no security scanning tools were detected. This is a modest transparency and hygiene gap, not evidence that the package is unsafe by itself.
No repository security policy was found. For a package intended to run application diagnostics, the missing reporting and response process lowers transparency, though it is less serious than stalled release and commit activity.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all 3 of 3 action references are unpinned, which leaves the build exposed to moving action code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/semver Version ^1.4|^3.0 | — | — |
geerlingguy/ping Version ^1.1 | — | — |
vlucas/phpdotenv Version ~2.5|~3.3|^4.0|^5.0 | — | — |
illuminate/support Version 5.2.*|5.3.*|5.4.*|5.5.*|5.6.*|5.7.*|5.8.*|^6.0|^7.0|^8.0|^9.0|^10.0 | — | — |
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.