bazelbuild/bazel-central-registry

0

/ 100

Documentation58
Engineering83
Health100
Starlark373Apache-2.01d ago
Grade a repo

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

The central registry of Bazel modules for the Bzlmod external dependency system.

Documentation

58

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt48

README is present.

Contributing guide5pt53

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.

License6pt100

Licensed under Apache-2.0.

Engineering

83

CI/CD14pt72

CI is configured (.github/workflows/pre-commit.yml).

Tests18pt80

Test files detected (modules/aom/3.13.3/overlay/test).

Reproducibility6pt90

Lockfile present (modules/boost.python/1.83.0/overlay/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (modules/boost.python/1.83.0/overlay/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)
  • 793
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 11h
    Median issue response
  • 3h
    Median PR merge time
  • 269
    Open issues
Repository files26 root entries
  • .agent
  • .bazelci
  • .gemini
  • .github
    Good: CI is configured (.github/workflows/pre-commit.yml).
    Good: Dependabot covers 3 ecosystems (github-actions, npm, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • docs
    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).
    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.
  • modules
    Good: Test files detected (modules/aom/3.13.3/overlay/test).
    Good: Lockfile present (modules/boost.python/1.83.0/overlay/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (modules/boost.python/1.83.0/overlay/requirements.txt).
  • tools
  • .bazelignore
  • .bazelversion
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • .ruff.toml
  • AUTHORS
  • bazel_registry.json
  • BUILD
  • CODEOWNERS
  • GEMINI.md
  • incompatible_flags.yml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • metadata.schema.json
  • MODULE.bazel
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • WORKSPACE