block/buzz
Grade a repo

95

/ 100

GradeA

Excellent work. The main thing left to polish is dependency metadata.

Top 7% of 5,156 graded repos

A hive mind communication platform

Documentation95
Engineering96
Health86
Rust35,299Apache-2.09d ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

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

  4. 4
    README12pt

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

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

95

README12pt90

README is present.

Contributing guide5pt93

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

96

CI/CD14pt85

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

Tests18pt100

Test files detected (.github/scripts/codex-security-review.test.js).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

Dependency manifest found (Cargo.toml).

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

  • 133 / 1541
    Commits (30d / 90d)
  • 4,654
    Forks
  • 122
    Releaseslatest 5mo ago

Community

  • 100% - Good
    Community health
  • -
    authors own >50% of commits
  • 35,299
    Watchers

Responsiveness

  • 17h
    Median issue response
  • <1h
    Median PR merge time
  • 3,614
    Open issues
Repository files75 root entries
  • .agents
  • .cargo
  • .claude
  • .codex
  • .config
  • .github
    Good: Test files detected (.github/scripts/codex-security-review.test.js).
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Environment pinned via .github/ci/minio/Dockerfile.
    Good: Issue or PR templates present.
  • .goose
  • .intersect
  • .release
  • .vscode
  • admin-web
  • benchmarks
  • bin
  • crates
  • deploy
  • desktop
  • docs
  • examples
  • migrations
  • mobile
  • patches
  • perf
  • PLANS
  • schema
  • script
  • scripts
  • test-fixtures
  • web
  • .dockerignore
  • .env.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • ARCHITECTURE.md
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTEXT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • ct.yaml
  • deny.toml
  • docker-compose.ci.yml
  • docker-compose.harness.yml
  • docker-compose.yml
  • Dockerfile
  • Dockerfile.push-gateway
  • Dockerfile.sprig
  • GOVERNANCE.md
  • Justfile
  • lefthook.yml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOSTR.md
  • package.json
  • pnpm-lock.yaml
  • pnpm-workspace.yaml
  • preview-features.json
  • prometheus.yml
  • 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.
  • RELEASING.md
  • renovate.json
    Good: Renovate is configured (renovate.json). Dependencies update automatically across every package manager it detects.
  • rust-toolchain.toml
  • SECURITY.md
    Good: Security policy present.
  • TESTING.md
  • VISION_ACTIVITY.md
  • VISION_AGENT.md
  • VISION_MESH.md
  • VISION_MOBILE.md
  • VISION_MODERATION.md
  • VISION_PROJECTS.md
  • VISION_REMOTE_AGENTS.md
  • VISION_SOVEREIGN.md
  • VISION.md
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/block/buzz)](https://www.repo-grade.com/report/block/buzz)

More graded Rust repos