The README, MIT license, and matching repository make setup and ownership reasonably clear. However, the last release and repository push were in December 2017, with no recent commits and no security policy, so maintenance risk is substantial.
38%
Total Score
25
100
75
75
The package has had no releases in more than 8 years, and all 12 releases arrived during its initial short publishing period. This is strong evidence of abandonment risk despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push being in December 2017. No provided signal shows compensating recent maintenance.
Registry publishing access is held by one maintainer, and the repository owner is an individual rather than an organization. Combined with the long period of inactivity, this leaves limited visible maintenance capacity.
The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these counts provide no visible community activity to offset the maintenance concerns.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cviebrock/eloquent-sluggable Version ^4.3 | — | — |
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.