83

/ 100

GradeB

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

Top 26% of 5,156 graded repos

BuildBuddy is an open source Bazel build event viewer, result store, remote cache, and remote build execution platform.

Top fixes

Highest-impact changes first, ranked by point weight

19 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 a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

77

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt52

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

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

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

86

CI/CD14pt57

CI is configured (.github/workflows/build-executor-win.yaml).

Reproducibility6pt85

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (cli/arg/arg_test.go).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (go.mod).

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

  • 200 / 833
    Commits (30d / 90d)
  • 139
    Forks
  • 369
    Releaseslatest 5y ago

Community

  • 100% - Good
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 757
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 3h
    Median PR merge time
  • 196
    Open issues
Repository files61 root entries
  • .github
    Good: CI is configured (.github/workflows/build-executor-win.yaml).
    Good: Issue or PR templates present.
  • app
  • apt
  • aws_rds_certs
  • buildpatches
  • cli
    Good: Test files detected (cli/arg/arg_test.go).
  • codesearch
  • config
  • deployment
  • deps
  • dockerfiles
    Good: Environment pinned via dockerfiles/default_execution_image/Dockerfile.
  • docs
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • enterprise
  • images
  • platforms
  • proto
  • rules
  • server
  • static
  • terraform
  • third_party
  • toolchains
  • tools
  • website
  • .bazelignore
  • .bazelrc
  • .bazelversion
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .prettierignore
  • .prettierrc
  • .swcrc
  • bazel_downloader.cfg
  • BUILD
  • buildbuddy.yaml
  • buildfix.sh
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • deps.bzl
  • gazelle_python.yaml
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • k8s_on_prem.sh
  • LICENSE
    Good: Licensed under Other.
  • MODULE.bazel
  • MODULE.bazel.lock
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • prodaccess.sh
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • release.py
  • requirements.lock
  • requirements.txt
  • SECURITY.md
    Good: Security policy present.
  • shared.bazelrc
  • template-user.bazelrc
  • tsconfig.json
  • WORKSPACE
  • workspace_status.sh
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/buildbuddy-io/buildbuddy)](https://www.repo-grade.com/report/buildbuddy-io/buildbuddy)

More graded Go repos