remix-run/remix
Grade a repo

87

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 14% of 5,156 graded repos

Build Better Websites. Create modern, resilient user experiences with web fundamentals.

Documentation95
Engineering85
Health89
TypeScript33,177MIT24d ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  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
    Dependency manifest6pt

    Add a one-line description to package.json. It appears in npm search and on GitHub.

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

95

README12pt90

README is present.

Contributing guide5pt92

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

85

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.

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (demos/bookstore/app/actions/account/controller.test.ts).

CI/CD14pt100

CI is configured (.github/workflows/check-main.yaml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Project health

89

Dependency manifest6pt65

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

  • 28 / 357
    Commits (30d / 90d)
  • 2,780
    Forks
  • 602
    Releaseslatest 5y ago

Community

  • 62% - Fair
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 33,177
    Watchers

Responsiveness

  • 1d 4h
    Median issue response
  • 17h
    Median PR merge time
  • 61
    Open issues
Repository files25 root entries
  • .agents
  • .codex
  • .github
    Good: CI is configured (.github/workflows/check-main.yaml).
  • .vscode
  • decisions
  • demos
    Good: Test files detected (demos/bookstore/app/actions/account/controller.test.ts).
  • docs
  • packages
  • scripts
  • template
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
    Good: Environment pinned via .nvmrc.
  • .oxlintrc.json
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • AGENTS.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • cspell.yml
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • 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.
    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.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
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/remix-run/remix)](https://www.repo-grade.com/report/remix-run/remix)

More graded TypeScript repos