antiwork/gumroad

0

/ 100

Documentation91
Engineering78
Health100
Ruby9,259MIT5d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

Sell stuff and see what sticks

Documentation

91

README12pt80

README is present.

Contributing guide5pt88

Contributing guide is detailed and thorough.

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/utils/currency.test.ts).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/tests.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 files60 root entries
  • .agents
  • .buildkite
  • .claude
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
  • .vscode
  • app
    Good: Test files detected (app/javascript/utils/currency.test.ts).
  • bin
  • ci_scripts
  • config
  • db
  • docker
    Good: Environment pinned via docker/base/Dockerfile.
  • docs
  • lib
  • log
  • patches
  • public
  • qa-media
  • scripts
  • spec
  • 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
  • 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.
    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.
    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