0
/ 100
Solid engineering. The biggest lever is issue and PR templates.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
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
70
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.
Licensed under Apache-2.0.
Engineering
85
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.
Test files detected (packages/mcp-relay/src/__tests__).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (lint script in package.json).
Project health
73
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 13Releaseslatest 2mo ago
Community
- 25% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 1Open issues
Repository files15 root entries
- .claude-plugin
- .githubGood: CI is configured (.github/workflows/ci.yml).
- packagesGood: Test files detected (packages/mcp-relay/src/__tests__).
- .fallowrc.json
- .gitignoreGood: .gitignore present.
- .node-versionGood: Environment pinned via .node-version.
- .npmrc
- .releaserc.json
- DEVELOPMENT.md
- lefthook.yml
- LICENSEGood: Licensed under Apache-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- renovate.json5
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/archon-research/uikit)