Documentation, licensing, and a small dependency surface make its intended use clear. However, maintenance has stopped for nearly six years, so compatibility and support risk are substantial.
40%
Total Score
25
100
75
75
The latest release was nearly six years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having a stable release history.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance to offset the concern.
The package and repository are owned by the same individual account, so the source appears correctly connected rather than organization-backed. This offers limited maintenance capacity but is not itself a health failure.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a minor transparency and hygiene concern, not a standalone adoption blocker.
The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This adds a transparency gap, especially alongside the lack of recent maintenance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-dashboard Version ^2.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.