cviebrock/eloquent-sluggable

Easy creation of slugs for your Eloquent models in Laravel

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 17th, 2026
Created on June 5th, 2013
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 452
Total Stargazers: 3,999 (+0)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.3 hours
Mean response time: 25.3 hours
90th percentile: 3.4 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)
  • triaged (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Eloquent-Sluggable is a Laravel package that automatically generates URL-friendly slugs for your Eloquent models.

The package solves the problem of creating readable, SEO-friendly URLs by converting model attributes into slugs—simplified strings with spaces and special characters removed, suitable for use in URLs. It handles the common requirement that slugs be unique by automatically appending numeric suffixes when duplicates are detected, so multiple posts with the same title can coexist with distinct URLs like my-dinner-with-andre-francois, my-dinner-with-andre-francois-1, and my-dinner-with-andre-francois-2.

Developers should choose this tool when building Laravel applications that need human-readable URLs for resources like blog posts, products, or other content. The package integrates directly into Eloquent models through a trait-based approach and works with route model binding, making it suitable for any Laravel project where slug generation would otherwise require manual implementation. Configuration is flexible, supporting options for slug source fields, separator characters, uniqueness constraints, maximum length, reserved words, and custom slug engine behavior. The README does not compare the package to alternatives.

Work in the issue tracker is dominated by enhancement requests and triaged issues, indicating active curation of feature requests and bug reports.