78
/ 100
Solid engineering. The biggest lever is CI.
Native macOS and iOS App for the Hermes AI agent — multi-window, multi-server (local + remote over SSH). Chat, dashboard, sessions, memory, cron, MCP, and more.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
95
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
58
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit Package.resolved for application projects so Swift Package Manager resolves the same versions.
CI is configured (.github/workflows/validate-template-pr.yml).
Test files detected (scarf/Packages/ScarfCore/Tests).
Issue or PR templates present.
Project health
100
Dependency manifest found (scarf/Packages/ScarfCore/Package.swift).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 115 / 559Commits (30d / 90d)
- 46Forks
- 44Releaseslatest 4mo ago
Community
- 71% - FairCommunity health
- 1 bus factorlowauthor own >50% of commits
- 721Watchers
Responsiveness
- 6hMedian issue response
- <1hMedian PR merge time
- 3Open issues
Repository files30 root entries
- .codex
- .cursor
- .gemini
- .githubGood: CI is configured (.github/workflows/validate-template-pr.yml).Good: Issue or PR templates present.
- .memory
- assets
- code
- design
- documents
- releases
- scarfGood: Test files detected (scarf/Packages/ScarfCore/Tests).Good: Dependency manifest found (scarf/Packages/ScarfCore/Package.swift).
- scripts
- sessions
- site
- tasks
- templates
- tools
- vendors
- wiki
- .gitignoreGood: .gitignore present.
- .mcp.json
- AGENTS.md
- BUILDING.md
- CLAUDE.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.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.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.
- GEMINI.md
- icon-v2.5.png
- LICENSEGood: Licensed under MIT.
- 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.
- TASKS.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/awizemann/scarf)