envoyproxy/nighthawk
Grade a repo

0

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 26% of 5,156 graded repos

L7 (HTTP/HTTPS/HTTP2/HTTP3) performance characterization tool

Documentation91
Engineering70
Health100
C++409Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

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

  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

91

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

70

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

CI/CD14pt57

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

Tests18pt80

Test files detected (benchmarks/dynamic_test/test_cds_churn_with_traffic.py).

Reproducibility6pt100

Lockfile present (tools/base/requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (tools/base/requirements.txt).

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

  • -
    Commits (30d / 90d)
  • 92
    Forks
  • 4
    Releaseslatest 4y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 409
    Watchers

Responsiveness

  • 65d 2h
    Median issue response
  • 7h
    Median PR merge time
  • 176
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/_ci.yml).
    Good: Dependabot covers 3 ecosystems (docker, docker, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .vscode
  • api
  • bazel
  • benchmarks
    Good: Test files detected (benchmarks/dynamic_test/test_cds_churn_with_traffic.py).
  • ci
    Good: Environment pinned via ci/docker-compose.yml.
  • docs
  • dynamic_config
  • include
  • internal_proto
  • samples
  • source
  • support
  • test
  • tools
    Good: Lockfile present (tools/base/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (tools/base/requirements.txt).
  • .bazelrc
  • .bazelversion
  • .clang-format
  • .clang-tidy
  • .gitignore
    Good: .gitignore present.
  • BUILD
  • CHANGELOG.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • extensions_build_config.bzl
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MAINTAINERS.md
  • nighthawk.code-workspace
  • OWNERS.md
  • PROFILING.md
  • README.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RELEASE_PROCEDURE.md
  • repokitteh.star
  • WORKSPACE
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/nighthawk)](https://www.repo-grade.com/report/envoyproxy/nighthawk)

More graded C++ repos