envoyproxy/envoy-website

0

/ 100

Documentation74
Engineering29
Health86
SCSS48Apache-2.01d ago
Grade a repo

Getting some notice. Tests and CI would be the fastest wins.

Envoy Proxy website

Documentation

74

Contributing guide5pt25

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

29

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

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.

Issue and PR templates6pt0

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/CD14pt57

CI is configured (.github/workflows/macos-build.yml).

Reproducibility6pt100

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

Project health

86

Dependency manifest6pt55

Dependency manifest found (package.json).

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)
  • 187
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 48
    Watchers

Responsiveness

  • 12h
    Median issue response
  • <1h
    Median PR merge time
  • 17
    Open issues
Repository files27 root entries
  • .github
    Good: CI is configured (.github/workflows/macos-build.yml).
    Good: Dependabot covers 3 ecosystems (docker, github-actions, npm). Dependencies stay current.
  • bazel
  • site
  • .bazelrc
  • .bazelversion
  • .gitignore
    Good: .gitignore present.
  • .gitpod.yml
  • .node-version
  • .yamllint
  • archive.bzl
  • BUILD
  • build-website.sh
  • deps.bzl
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • netlify-should-run.sh
  • netlify.toml
  • package.json
    Good: Dependency manifest found (package.json).
  • packages.bzl
  • README.md
    Good: 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.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.