77
/ 100
Well engineered. The main gaps are issue and PR templates and a contributing guide.
Open-source AI gateway on Cloudflare Workers, in TypeScript: OpenAI/Anthropic-compatible chat with SSE streaming, Files + Batch APIs, provider routing with circuit breaking and failover, virtual API keys, per-tenant Durable Object storage, quotas/wallets/budgets, guardrails, response cache, MCP server, durable metering, contract-driven Admin API.
Top fixes
Highest-impact changes first, ranked by point weight
- 1README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 2Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.
- 3Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
- 4Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
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 is present.
README documents how to install the project.
Licensed under Other.
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 (bun.lock). Installs are reproducible.
Test files detected (admin-console/e2e/accessibility.spec.ts).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (admin-console/eslint.config.js).
Project health
92
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)
- 3Forks
- 40Releaseslatest 3mo ago
Community
- 57% - FairCommunity health
- -authors own >50% of commits
- 29Watchers
Responsiveness
- 8hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files28 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- admin-consoleGood: Test files detected (admin-console/e2e/accessibility.spec.ts).Good: Linter or formatter configured (admin-console/eslint.config.js).Good: Environment pinned via admin-console/Dockerfile.
- apps
- charts
- config
- deploy
- docs
- e2e
- Ferrogate
- ferrogate-wiki
- packages
- scripts
- sdks
- skills
- sql
- tests
- tools
- .dockerignore
- .gitignoreGood: .gitignore present.
- biome.jsonc
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- LICENSEGood: Licensed under Other.
- package.jsonGood: Dependency manifest found (package.json).
- 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.
- README.zh-CN.md
- SECURITY.mdGood: Security policy present.
- tsconfig.base.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/lianluo-esign/ferrogate)