yuges-code/laravel-sluggable

Release historydanger

The package is 686 days old but has only four releases, all concentrated in its first few days, with no releases in the last 12 months. This is a meaningful abandonment concern despite the package not being deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap and indicating little current maintenance capacity.

Maintainerscaution

Only one registry publishing account is listed, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops publishing.

Repo popularitycaution

The repository has two stars, zero forks, and one watcher, providing little external evidence of adoption or community review. Popularity is supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is present. This is a modest supply-chain hygiene gap rather than evidence that the release is unsafe.