Popular for its size, but the engineering basics lag behind the interest.
A modern, lightweight Markdown editor for macOS.
Documentation
93
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
A license file is present.
Engineering
35
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No RuboCop config found.
→ Add a .rubocop.yml and run `rubocop` in CI to enforce consistent Ruby style.
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 is configured (.github/workflows/build-release.yml).
Lockfile present (Gemfile.lock). Installs are reproducible.
Project health
100
Dependency manifest found (Gemfile).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 34Forks
- 12Releaseslatest 4mo ago
Community
- —Community health
- —authors own >50% of commits
- 344Watchers
Responsiveness
- 7d 13hMedian issue response
- <1hMedian PR merge time
- 89Open issues
Repository files31 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/build-release.yml).Good: Dependabot covers 2 ecosystems (bundler, npm). Dependencies stay current.
- assets
- Dependency
- docs
- LICENSEGood: A license file is present.
- MacDown
- MacDown 3000.xcodeproj
- MacDown 3000.xcworkspace
- macdown-cmd
- MacDownCore
- MacDownQuickLook
- MacDownTests
- notes
- plans
- scripts
- Tools
- .envrc.example
- .gitignoreGood: .gitignore present.
- .gitmodules
- .markdownlint.json
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.mdGood: 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.
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- PLAN.md
- Podfile
- Podfile.lock
- README.mdGood: 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