94

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 7% of 5,156 graded repos

High-performance, ESLint-compatible linter for JavaScript and TypeScript.

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  2. 2
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  4. 4
    Reproducibility6pt

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

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

89

Contributing guide5pt83

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.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

97

Reproducibility6pt75

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

Tests18pt100

Test files detected (cmd/rslint/api_test.go).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt92

Dependency manifest found (Cargo.toml).

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

  • -
    Commits (30d / 90d)
  • 22
    Forks
  • 29
    Releaseslatest 8mo ago

Community

  • 75% - Good
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 409
    Watchers

Responsiveness

  • 4d 10h
    Median issue response
  • <1h
    Median PR merge time
  • 48
    Open issues
Repository files44 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • cmd
    Good: Test files detected (cmd/rslint/api_test.go).
  • crates
  • internal
  • npm
  • packages
  • scripts
  • shim
  • tests
  • tools
  • website
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .golangci.yml
    Good: Linter or formatter configured (.golangci.yml).
  • .prettierignore
  • .prettierrc
  • AGENTS.md
  • architecture.md
  • ast-grep-rule.yml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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.
    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.
    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.
    Good: Contributing guide includes code examples.
  • cspell.config.cjs
  • go.mod
  • go.sum
  • go.work
  • go.work.sum
  • LICENSE
    Good: Licensed under MIT.
  • package.json
  • pnpm-lock.yaml
  • 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.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rslint-schema.json
  • rslint.config.ts
  • skills-lock.json
  • tsconfig.base.json
  • tsconfig.build.json
  • tsconfig.json
  • tsconfig.spec.json
  • typescript-go
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/web-infra-dev/rslint)](https://www.repo-grade.com/report/web-infra-dev/rslint)

More graded Go repos