norman/friendly_id

FriendlyId is the “Swiss Army bulldozer” of slugging and permalink plugins for ActiveRecord. It allows you to create pretty URL’s and work with...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 10th, 2026
Created on April 18th, 2008
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 591
Total Stargazers: 6,225 (+0)
Total Subscribers: 55 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 191.9 days
Mean response time: 300.6 days
90th percentile: 585.6 days
Tracked items: 10

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,223 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

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

Top labels

  • pinned (2)
  • Bug (1)
  • Looking for help (1)
  • stale (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

FriendlyId is a Ruby on Rails plugin that generates human-readable URL slugs and allows ActiveRecord models to be queried using friendly strings instead of numeric identifiers.

The problem FriendlyId solves is the need to create clean, readable URLs and work with meaningful identifiers in web applications. Rather than exposing database IDs in URLs, the tool generates slugs from model attributes—typically titles or names—and lets you treat these slugs as primary identifiers throughout your application. This means you can query records by their friendly string identifier as easily as by their numeric ID, and the URLs become more descriptive and SEO-friendly.

FriendlyId suits Rails applications where user-facing URLs matter, such as blogs, content management systems, or any site where readable permalinks improve usability and search visibility. It integrates directly with ActiveRecord, so it works naturally within the Rails ecosystem without requiring architectural changes. The tool handles common slug-generation concerns like uniqueness, history tracking, and fallback behavior when friendly identifiers collide or change.

Development on the project shows consistent maintenance with regular updates addressing bugs and compatibility issues. The codebase receives ongoing attention to keep it aligned with current Rails versions and Ruby practices. Pull requests are reviewed and merged steadily, indicating active stewardship of the tool's quality and reliability.