A single maintainer, no security scanning or policy, and zero repository activity reduce confidence in ongoing support. The MIT license, clear README, changelog, and non-deprecated status provide useful transparency.
42%
Total Score
33
100
67
50
The package published 40 releases in a single burst on June 17, 2022, then had no releases in the following 12 months; it has been inactive for over four years. This is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the last push being over four years ago, this indicates a high abandonment risk.
Only one registry account has publish access. The linked repository is user-owned rather than organization-backed, so there is little visible publishing redundancy.
The published artifact includes a 2,203-character README and a changelog; the absence of packaged tests is normal for a published library artifact. Repository tests are also absent, so there is no testing evidence to offset maintenance concerns.
The repository owner is an individual user, not an organization, and no stronger institutional backing is shown. That leaves limited visible continuity support for a package with no recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/nova Version ^4.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.