The small user base and missing security policy provide little evidence of ongoing support or security processes. Clear licensing, documentation, and package-to-repository alignment reduce adoption friction, but not the maintenance concern.
45%
Total Score
50
100
81
75
The package has had only 2 releases, both published about 4 years ago, with 0 releases in the last 12 months. This is strong evidence of stalled maintenance for a dependency that may need compatibility updates.
Only one registry publishing account is listed. A single maintainer creates a thin support base and increases abandonment risk, with no organizational backing shown to compensate.
The repository has 0 stars, 2 forks, and 1 watcher, providing little evidence of an active user or contributor community. Popularity is supporting evidence rather than decisive on its own, so this is a modest concern.
The repository has no security policy, so there is no documented channel or process for handling vulnerabilities. This is a transparency and response-process gap, though it is less serious than the stalled release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
dcat/laravel-admin Version ~2.0 | — | — |
spatie/eloquent-sortable Version 3.*|4.* | — | — |
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.