homebrew/homebrew-cask
Grade a repo

63

/ 100

GradeD

A workable base with real gaps. Start with test coverage and CI.

Higher than 47% of 5,156 graded repos

🍻 A CLI workflow for the administration of macOS applications distributed as binaries

Documentation94
Engineering41
Health68
Ruby22,151BSD-2-Clause1d 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 B (88).

See your top fixes
Now
D
63
Potential
B
88

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under BSD-2-Clause.

Engineering

41

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Reproducibility6pt22

No dependency lockfile found (−70 pts).

→ Commit Gemfile.lock so Bundler installs are repeatable.

CI/CD14pt57

CI is configured (.github/workflows/check-issues.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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

  • 10201 / 31585
    Commits (30d / 90d)
  • 11,794
    Forks
  • 81
    Releaseslatest 12y ago

Community

  • 87% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 22,151
    Watchers

Responsiveness

  • 12h
    Median issue response
  • 7h
    Median PR merge time
  • 45
    Open issues
Repository files19 root entries
  • .github
    Good: CI is configured (.github/workflows/check-issues.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • audit_exceptions
  • Casks
  • cmd
  • developer
  • doc
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .rubocop.yml
  • .ruby-version
    Good: Environment pinned via .ruby-version.
  • AGENTS.md
  • cask_renames.json
  • CLAUDE.md
  • 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.
    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.
  • LICENSE
    Good: Licensed under BSD-2-Clause.
  • 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.
  • tap_migrations.json
  • USAGE.md
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/homebrew/homebrew-cask)](https://www.repo-grade.com/report/homebrew/homebrew-cask)

More graded Ruby repos