voormedia/rails-erd

Generate Entity-Relationship Diagrams for Rails applications

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 16th, 2026
Created on September 19th, 2010
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 380
Total Stargazers: 4,102 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 78.3 days
Mean response time: 667.8 days
90th percentile: 2477.3 days
Tracked items: 103

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 20 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 (18)
  • Beginner (9)
  • Bug (9)
  • Documentation (9)
  • New Feature (6)
  • Needs More Info (3)
  • JRuby (1)
  • Rails 6 (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

rails-erd is a diagram generation tool that creates Entity-Relationship Diagrams for Rails applications.

The tool solves the problem of visualizing database schema and model relationships in Rails projects. It works by inspecting the Rails application's models and their associations, then generating a visual diagram that represents the database structure. This allows developers to see at a glance how their models relate to one another and understand the overall architecture of their data layer.

The tool is well-suited for Rails developers who want to document their application's schema or understand an unfamiliar codebase's data structure. It works directly with Rails conventions, requiring no separate schema definitions or configuration files beyond what already exists in the application. This makes it particularly useful for teams onboarding new developers or for creating documentation of existing systems. The generated diagrams can help identify design issues or validate that the schema matches the intended model relationships.

The project maintains a stable, established codebase with infrequent but deliberate updates. Pull requests are reviewed and merged selectively, indicating careful stewardship of the tool's direction. The maintainers respond to issues and accept contributions, though the pace of activity reflects a mature project that has reached a stable state rather than one undergoing active feature expansion.