89

/ 100

GradeB

Well engineered. The main gap is issue and PR templates.

Top 14% of 5,156 graded repos

See what sticks

Top fixes

Highest-impact changes first, ranked by point weight

5 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
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  3. 3
    Issue and PR templates6pt

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

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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

98

Contributing guide5pt88

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

78

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.

Tests18pt80

Test files detected (app/javascript/components/Admin/Purchases/index.test.tsx).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/ci-green.yml).

Linting and formatting5pt100

Ruby linting configured (.prettierrc).

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

  • 522 / 1073
    Commits (30d / 90d)
  • 1,989
    Forks
  • 493
    Releaseslatest 4mo ago

Community

  • 62% - Fair
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 9,477
    Watchers

Responsiveness

  • 1d 1h
    Median issue response
  • <1h
    Median PR merge time
  • 20
    Open issues
Repository files62 root entries
  • .agents
  • .buildkite
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci-green.yml).
  • .vscode
  • app
    Good: Test files detected (app/javascript/components/Admin/Purchases/index.test.tsx).
  • bin
  • ci_scripts
  • config
  • db
  • docker
    Good: Environment pinned via docker/base/Dockerfile.
  • docs
  • lib
  • log
  • patches
  • public
  • qa-media
  • scripts
  • spec
  • test
  • vendor
  • .claudeignore
  • .cursorignore
  • .dockerignore
  • .env.development
  • .env.example
  • .env.production.example
  • .env.test
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .node-version
  • .npmrc
  • .prettierignore
  • .prettierrc
    Good: Ruby linting configured (.prettierrc).
  • .rspec
  • .rubocop.yml
  • .ruby-version
  • AGENTS.md
  • auto-imports.d.ts
  • CLAUDE.md
  • config.ru
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • eslint.config.js
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • LICENSE.md
    Good: Licensed under MIT.
  • Makefile
  • package-lock.json
  • package.json
  • postcss.config.js
  • Procfile.debug
  • Procfile.dev
  • Rakefile
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • TRADEMARK_GUIDELINES.md
  • tsconfig.json
  • vite.config.ts
  • vite.config.widget.ts
  • vitest.config.ts
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/antiwork/gumroad)](https://www.repo-grade.com/report/antiwork/gumroad)

More graded Ruby repos