54
/ 100
Getting some notice. Tests and CI would be the fastest wins.
Envoy Proxy website
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (82).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Add automated tests. They prove the code works and give contributors confidence to make changes.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 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
74
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 Apache-2.0.
Engineering
29
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/macos-build.yml).
Lockfile present (yarn.lock). Installs are reproducible.
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)
- 187Forks
- 0Releases
Community
- 37% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 48Watchers
Responsiveness
- 12hMedian issue response
- <1hMedian PR merge time
- 17Open issues
Repository files27 root entries
- .githubGood: CI is configured (.github/workflows/macos-build.yml).Good: Dependabot covers 3 ecosystems (docker, github-actions, npm). Dependencies stay current.
- bazel
- site
- .bazelrc
- .bazelversion
- .gitignoreGood: .gitignore present.
- .gitpod.yml
- .node-version
- .yamllint
- archive.bzl
- BUILD
- build-website.sh
- deps.bzl
- docker-compose.ymlGood: Environment pinned via docker-compose.yml.
- LICENSEGood: Licensed under Apache-2.0.
- netlify-should-run.sh
- netlify.toml
- package.jsonGood: Dependency manifest found (package.json).
- packages.bzl
- 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.
- rebuild.sh
- sync_archive.sh
- sync_envoy.sh
- toolchains.bzl
- versions.bzl
- WORKSPACE
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/envoyproxy/envoy-website)