envoyproxy/envoy
Grade a repo

88

/ 100

GradeB

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 16% of 5,156 graded repos

Cloud-native high-performance edge/middle/service proxy

Documentation88
Engineering83
Health100
C++28,469Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

88

Contributing guide5pt77

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

83

CI/CD14pt40

CI is configured (.github/workflows/_check_build.yml).

Tests18pt100

Test files detected (api/test).

Linting and formatting5pt100

Rust linting configured (.flake8).

Reproducibility6pt100

Lockfile present (Cargo.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 271 / 933
    Commits (30d / 90d)
  • 5,454
    Forks
  • 273
    Releaseslatest 7y ago

Community

  • 100% - Good
    Community health
  • 10 bus factor
    authors own >50% of commits
  • 28,469
    Watchers

Responsiveness

  • 1d 8h
    Median issue response
  • <1h
    Median PR merge time
  • 1,835
    Open issues
Repository files76 root entries
  • .agents
  • .bazelci
  • .bcr
  • .devcontainer
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/_check_build.yml).
    Good: Dependabot covers 16 ecosystems (pip, pip, pip, docker, docker, docker, docker, github-actions, gomod, gomod, gomod, gomod, gomod, gomod, gomod, gomod). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • api
    Good: Test files detected (api/test).
  • bazel
  • changelogs
  • ci
    Good: Environment pinned via ci/docker-compose.yml.
  • compat
  • configs
  • contrib
  • distribution
  • docs
  • envoy
  • maintainer
  • mobile
  • restarter
  • security
  • source
  • support
  • test
  • third_party
  • tools
  • .bazelignore
  • .bazelrc
  • .bazelversion
  • .clang-format
  • .clang-tidy
  • .coveragerc
  • .dockerignore
  • .flake8
    Good: Rust linting configured (.flake8).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .yamllint
  • AGENTS.md
  • API_VERSION.txt
  • BACKPORTS.md
  • BUILD
  • Cargo.Bazel.lock
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEOWNERS
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • DCO
  • DEPENDENCY_POLICY.md
  • DEPRECATED.md
  • DEVELOPER.md
  • EXTENSION_POLICY.md
  • go.mod
  • go.sum
  • GOVERNANCE.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.bazel
  • MODULE.bazel.lock
  • NOTICE
  • OWNERS.md
  • PULL_REQUEST_TEMPLATE.md
  • PULL_REQUESTS.md
  • pytest.ini
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • releases.asc
  • RELEASES.md
  • REPO_LAYOUT.md
  • repokitteh.star
  • reviewers.yaml
  • rustfmt.toml
  • SECURITY-INSIGHTS.yml
  • SECURITY.md
    Good: Security policy present.
  • STYLE.md
  • VERSION.txt
  • WORKSPACE
  • WORKSPACE.bzlmod
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/envoyproxy/envoy)](https://www.repo-grade.com/report/envoyproxy/envoy)

More graded C++ repos