thoughtbot/guides
Grade a repo

54

/ 100

GradeF

Early-stage engineering. The fastest wins are test coverage and setup instructions.

Higher than 39% of 5,156 graded repos

A guide for programming in style.

Documentation37
Engineering49
Health94
Ruby9,5605d ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (75).

See your top fixes
Now
F
54
Potential
C
75

Top fixes

Highest-impact changes first, ranked by point weight

21 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

37

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt58

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt75

README is present.

Engineering

49

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt35

Test files detected (testing-rspec/acceptance_test_spec.rb).

CI/CD14pt57

CI is configured (.github/workflows/linting.yml).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (javascript-typescript/.eslintrc.json).

Project health

94

Dependency manifest6pt82

Dependency manifest found (package.json).

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

  • 1 / 5
    Commits (30d / 90d)
  • 1,350
    Forks
  • 0
    Releases

Community

  • 50% - Fair
    Community health
  • -
    authors own >50% of commits
  • 9,560
    Watchers

Responsiveness

  • 3h
    Median issue response
  • 2d 9h
    Median PR merge time
  • 12
    Open issues
Repository files47 root entries
  • _template
  • .github
    Good: CI is configured (.github/workflows/linting.yml).
  • accessibility
  • android
  • bash
  • code-review
  • css
  • data
  • email
  • erb
  • general
  • git
  • graphql
  • html
  • ios
  • javascript-typescript
    Good: Linter or formatter configured (javascript-typescript/.eslintrc.json).
  • object-oriented-design
  • open-source
  • postgres
  • product-review
  • production
  • python
  • rails
    Good: Security policy present.
  • react
  • react-native
  • relational-databases
  • ruby
  • sass
  • security
  • shell
  • swift
  • tech-stack
  • testing-jest
  • testing-rspec
    Good: Test files detected (testing-rspec/acceptance_test_spec.rb).
  • web
  • web-performance
  • .gitignore
    Good: .gitignore present.
  • .hound.yml
  • .markdownlint-cli2.jsonc
  • .tool-versions
    Good: Environment pinned via .tool-versions.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • lefthook.yml
  • mise.toml
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
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/thoughtbot/guides)](https://www.repo-grade.com/report/thoughtbot/guides)

More graded Ruby repos