bucketeer-io/bucketeer
Grade a repo

95

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 6% of 5,156 graded repos

Feature Flag Management and A/B Testing platform

Documentation88
Engineering100
Health94
Go475Apache-2.01mo ago

Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  2. 2
    Contributing guide5pt

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

  3. 3
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

  4. 4
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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 guide5pt47

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.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

100

Tests18pt100

Test files detected (evaluation/go/bucketeer_test.go).

CI/CD14pt100

CI is configured (.github/workflows/bigquery-emulator-build.yaml).

Linting and formatting5pt100

Formatting enforced (.golangci.yml).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 36
    Forks
  • 21
    Releaseslatest 2y ago

Community

  • 50% - Fair
    Community health
  • 3 bus factor
    authors own >50% of commits
  • 475
    Watchers

Responsiveness

  • 1d 14h
    Median issue response
  • 16h
    Median PR merge time
  • 52
    Open issues
Repository files33 root entries
  • .claude
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/bigquery-emulator-build.yaml).
    Good: Environment pinned via .github/.devcontainer/Dockerfile.
    Good: Dependabot covers 4 ecosystems (github-actions, gomod, gomod, npm). Dependencies stay current.
    Good: Issue or PR templates present.
  • api-description
  • cmd
  • docker-compose
  • docs
  • evaluation
    Good: Test files detected (evaluation/go/bucketeer_test.go).
  • hack
  • manifests
  • migration
  • pkg
  • proto
  • static-files
  • test
  • tools
  • ui
    Issue: Build artifacts or local files may be committed (ui/web-v2/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
    Good: Formatting enforced (.golangci.yml).
  • .release-please-manifest.json
  • CHANGELOG.md
  • CODEOWNERS
  • CONTRIBUTING.md
    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.
  • DEPLOYMENT.md
  • DEVELOPMENT.md
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • 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.
    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.
  • release-please-config.json
  • remove.sh
  • yarn.lock
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/bucketeer-io/bucketeer)](https://www.repo-grade.com/report/bucketeer-io/bucketeer)

More graded Go repos