0
/ 100
Solid foundation. Invest in docs and CI to grow from here.
AI assisted code review with a human in the loop
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a lint step to catch style issues automatically.
- 2CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.
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
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
70
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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.
Lockfile present (package-lock.json). Installs are reproducible.
CI is configured (.github/workflows/test.yml).
Test files detected (tests).
Project health
97
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)
- 15Forks
- 84Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 39Watchers
Responsiveness
- 4d 23hMedian issue response
- 3hMedian PR merge time
- 75Open issues
Repository files32 root entries
- .changeset
- .claude
- .claude-plugin
- .entireGood: .gitignore present.
- .githubGood: CI is configured (.github/workflows/test.yml).
- .pair-review
- .pi
- bin
- docs
- plans
- plugin
- plugin-code-critic
- public
- review-output
- scripts
- src
- testsGood: Test files detected (tests).
- .gitattributes
- .gitignore
- .mcp.json
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- config.example.json
- config.managed.json
- LICENSEGood: Licensed under Apache-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.js
- pnpm-lock.yaml
- 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.
- vitest.config.js
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/in-the-loop-labs/pair-review)