writer/cerebro
Grade a repo

0

/ 100

GradeA

Well engineered for its size. A portfolio piece worth showing off.

Top 6% of 5,156 graded repos

Compliance superpowers for coding agents.

Documentation86
Engineering100
Health100
Go11Apache-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

6 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  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

86

Contributing guide5pt57

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.

README12pt80

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 (api/openapi_deviceauth_test.go).

CI/CD14pt100

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

Linting and formatting5pt100

Formatting enforced (.editorconfig).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

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

  • -
    Commits (30d / 90d)
  • 2
    Forks
  • 591
    Releaseslatest 3mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 11
    Watchers

Responsiveness

  • 52d 13h
    Median issue response
  • 3h
    Median PR merge time
  • 66
    Open issues
Repository files51 root entries
  • .deepsec
    Good: .gitignore present.
  • .factory
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 7 ecosystems (gomod, gomod, npm, pip, npm, docker, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .semgrep
  • .vscode
  • api
    Good: Test files detected (api/openapi_deviceauth_test.go).
  • cmd
  • deploy
  • devex
  • docs
  • examples
  • gen
  • internal
  • ops
  • policies
  • proto
  • schemas
  • scripts
  • sdk
  • sources
  • tools
  • .dockerignore
  • .editorconfig
    Good: Formatting enforced (.editorconfig).
  • .env.example
  • .gitignore
  • .golangci.yml
  • .goreleaser.yaml
  • .govulncheck-ignore
  • .infisical.json
  • .pre-commit-config.yaml
  • .spectral.yaml
  • .tool-versions
  • AGENTS.md
  • buf.gen.sdk.yaml
  • buf.gen.yaml
  • buf.yaml
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Good: Contributing guide includes code examples.
  • docker-compose.platform.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.runtime
  • 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
  • mkdocs.yml
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
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/writer/cerebro)](https://www.repo-grade.com/report/writer/cerebro)

More graded Go repos