Documentation, tests, and a changelog are present, and the package has a clear MIT license with no install-time scripts. Its single-user ownership, absent security policy, and no recent repository activity make long-term support uncertain.
58%
Total Score
50
90
75
A single registry maintainer is reasonable for a small user-owned project, but it provides little redundancy if that maintainer stops supporting the package. The repository's inactive recent history makes this thin base more significant.
The package has only five releases, all concentrated within about four days, and none in the last 12 months; the latest release is about two years old. This suggests limited ongoing maintenance.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long gap since the latest release. That raises abandonment risk even though the repository is not archived.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though not a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.5.0|~5.6.0|~5.7.0|~5.8.0|^6.0|^7.0|^8.0|^9.0|^10.0 | — | — |
illuminate/database Version ~5.5.0|~5.6.0|~5.7.0|~5.8.0|^6.0|^7.0|^8.0|^9.0|^10.0 | — | — |
spatie/laravel-activitylog Version * | — | — |
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.