kolpikov/laravel-slug

It has a clear README, a stable 1.0.1 version, and a very small dependency surface. The sole release was published about eight years ago, and the repository has had no commits for about seven years. No security policy or scanning is visible, increasing the maintenance risk.

Latest 1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about eight years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a library dependency.

Repo commit activity

The repository recorded no commits or active maintainers in the last three months, and its last push was about seven years ago. The repository is not archived, but that does not compensate for the prolonged inactivity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful community signal to offset the inactivity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk by itself.

Security policy

The repository has no security policy. For a small utility this is a limited gap, but it leaves vulnerability reporting and maintenance expectations unspecified.