schuyler/macdown3000
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Top 50% of 5,156 graded repos

A modern, lightweight Markdown editor for macOS.

Documentation93
Engineering35
Health100
Objective-C3441mo 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 (87).

See your top fixes
Now
D
66
Potential
B
87

Top fixes

Highest-impact changes first, ranked by point weight

13 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 lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    Install and run instructions9pt

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

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

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

A license file is present.

Engineering

35

Tests18pt0

No tests detected anywhere in the repository.

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

Linting and formatting5pt0

No RuboCop config found.

→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.

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.

CI/CD14pt85

CI is configured (.github/workflows/build-release.yml).

Reproducibility6pt90

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

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

  • -
    Commits (30d / 90d)
  • 34
    Forks
  • 12
    Releaseslatest 6mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 344
    Watchers

Responsiveness

  • 7d 13h
    Median issue response
  • <1h
    Median PR merge time
  • 89
    Open issues
Repository files31 root entries
  • .claude
  • .github
    Good: CI is configured (.github/workflows/build-release.yml).
    Good: Dependabot covers 2 ecosystems (bundler, npm). Dependencies stay current.
  • assets
  • Dependency
  • docs
  • LICENSE
    Good: A license file is present.
  • MacDown
  • MacDown 3000.xcodeproj
  • MacDown 3000.xcworkspace
  • macdown-cmd
  • MacDownCore
  • MacDownQuickLook
  • MacDownTests
  • notes
  • plans
  • scripts
  • Tools
  • .envrc.example
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .markdownlint.json
  • CHANGELOG.md
  • 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.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • PLAN.md
  • Podfile
  • Podfile.lock
  • 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.
  • setup.sh
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/schuyler/macdown3000)](https://www.repo-grade.com/report/schuyler/macdown3000)

More graded Objective-C repos