RolifyCommunity/rolify

Role management library with resource scoping

View on GitHub ↗Jump to charts ↓

RolifyCommunity/rolify has 3k+ stars and 350+ forks on GitHub, is written in Ruby, and was last pushed on Jan 24, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 55 minutes ago
Type:Library / SDKCategory(s):Identity, Auth & SecretsSecurity & Privacy
Added to GitGenius on September 21st, 2026
Created on June 3rd, 2011
Open Issues & Pull Requests: 152 (+0)
GitHub issues: Enabled
Number of forks: 396
Total Stargazers: 3,175 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 366.2 days
Mean response time: 856.0 days
90th percentile: 3852.1 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Rolify is a role management library that provides resource-scoped authorization for Ruby applications. It solves the problem of implementing flexible role-based access control by allowing developers to assign roles to users with fine-grained scoping to specific resources. The library integrates with ActiveRecord models to attach roles dynamically, enabling authorization checks that consider both the user's role and the particular resource being accessed.

Rolify suits projects that need role-based permissions beyond simple global role assignment. It works well for multi-tenant applications, platforms with hierarchical resource structures, or systems where the same user might have different roles in different contexts. The library is particularly valuable when authorization logic needs to answer questions like "does this user have the admin role for this specific project" rather than just "is this user an admin."

The project maintains active development with regular updates and engagement on issues and pull requests. The maintainers respond to community contributions and keep the codebase aligned with current Ruby and Rails practices. Documentation is actively maintained through the project's homepage, providing guidance for both basic and advanced use cases.