70
/ 100
Strong early engineering with some momentum.
Eval framework that ranks agentic coding frameworks (Superpowers, Compound Engineering, Agent Skills, GSD) by having each build the same spec with the same harness+model in isolated sandboxes, graded on a weighted evidence-based rubric: PRD adherence, code quality, speed, token spend
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 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
62
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Engineering
68
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/pages.yml).
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured (biome.json).
Project health
86
Dependency manifest found (package.json).
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)
- 1Forks
- 0Releases
Community
- 28% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 10Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 4Open issues
Repository files25 root entries
- .cursor
- .devcontainer
- .githubGood: CI is configured (.github/workflows/pages.yml).
- config
- designs
- docs
- infraGood: Environment pinned via infra/trial-image/Dockerfile.
- openspec
- pages
- scripts
- src
- targets
- testsGood: Test files detected (tests).
- .env.example
- .gitignoreGood: .gitignore present.
- biome.jsonGood: Linter or formatter configured (biome.json).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- CLAUDE.md
- package.jsonGood: Dependency manifest found (package.json).
- PROMPT_OPEN_SWE.md
- PROMPT.md
- 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.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- ROADMAP.md
- tsconfig.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/natea/harness-eval)