rails/rails
Grade a repo

83

/ 100

GradeB

Well engineered. The main gaps are setup instructions and the README.

Top 26% of 5,156 graded repos

Ruby on Rails

Documentation69
Engineering86
Health100
Ruby58,783MIT29d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

69

Install and run instructions9pt45

README documents how to install the project.

README12pt70

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

86

Tests18pt80

Test files detected (actioncable/bin/test).

Reproducibility6pt80

Lockfile present (Gemfile.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/devcontainer-shellcheck.yml).

Linting and formatting5pt100

Ruby linting configured (.rubocop.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 460 / 1262
    Commits (30d / 90d)
  • 22,404
    Forks
  • 165
    Releaseslatest 6y ago

Community

  • 87% - Good
    Community health
  • 13 bus factor
    authors own >50% of commits
  • 58,783
    Watchers

Responsiveness

  • 1h
    Median issue response
  • 10h
    Median PR merge time
  • 1,560
    Open issues
Repository files41 root entries
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/devcontainer-shellcheck.yml).
    Good: Issue or PR templates present.
    Good: Security policy present.
  • actioncable
    Good: Test files detected (actioncable/bin/test).
  • actionmailbox
  • actionmailer
  • actionpack
  • actiontext
  • actionview
  • activejob
  • activemodel
  • activerecord
  • activestorage
  • activesupport
  • bin
  • guides
  • railties
  • tasks
  • tools
    Good: Licensed under MIT.
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mdlrc
  • .mdlrc.rb
  • .rubocop.yml
    Good: Ruby linting configured (.rubocop.yml).
  • .yardopts
  • .yarnrc
  • AGENTS.md
  • Brewfile
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • eslint.config.mjs
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • MIT-LICENSE
  • package.json
  • RAILS_VERSION
  • rails.gemspec
  • Rakefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • RELEASING_RAILS.md
  • yarn.lock
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/rails/rails)](https://www.repo-grade.com/report/rails/rails)

More graded Ruby repos