0
/ 100
Good community traction and solid fundamentals. Nearly in the top tier.
Route, manage, and analyze your LLM requests across multiple providers with a unified API interface.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
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
73
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 Other.
Engineering
76
Test files detected (apps/api/src/api.spec.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.editorconfig).
Lockfile present (pnpm-lock.yaml). Installs are reproducible.
Issue or PR templates present.
Project health
89
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)
- 148Forks
- 6Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 1,343Watchers
Responsiveness
- 11d 19hMedian issue response
- <1hMedian PR merge time
- 60Open issues
Repository files44 root entries
- .agents
- .claude
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot covers 3 ecosystems (github-actions, docker, npm). Dependencies stay current.Good: Issue or PR templates present.
- .husky
- .run
- .vscode
- appsGood: Test files detected (apps/api/src/api.spec.ts).
- ee
- http
- infra
- legal
- packages
- patches
- scripts
- sql
- vitest
- .dockerignore
- .editorconfigGood: Linter or formatter configured (.editorconfig).
- .env.example
- .env.unified.example
- .gitignoreGood: .gitignore present.
- .mcp.json
- .npmrc
- .oneignore
- .tool-versions
- AGENTS.md
- CLAUDE.md
- conductor.json
- docker-compose.yml
- eslint.config.mjs
- findings.md
- hero-image.png
- LICENSEGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- pnpm-lock.yamlGood: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
- pnpm-workspace.yaml
- 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.
- skills-lock.json
- terragon-setup.sh
- tsconfig.json
- turbo.json
- vite.config.mts
- vitest.config.mts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/theopenco/llmgateway)