dicklesworthstone/beads_viewer
Grade a repo

0

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 14% of 5,156 graded repos

Graph-aware TUI for the Beads issue tracker: PageRank, critical path, kanban, dependency DAG visualization, and robot-mode JSON API

Documentation93
Engineering82
Health100
Go1,585Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

7 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
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

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

93

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

82

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt85

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

Reproducibility6pt85

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

Tests18pt100

Test files detected (bv-graph-wasm/tests).

Linting and formatting5pt100

Formatting enforced (vendor/github.com/alecthomas/chroma/v2/.editorconfig).

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)
  • 129
    Forks
  • 32
    Releaseslatest 7mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,585
    Watchers

Responsiveness

  • 5d 18h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files34 root entries
  • .beads
    Good: .gitignore present.
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .ntm
  • benchmarks
  • bv-graph-wasm
    Good: Test files detected (bv-graph-wasm/tests).
  • cmd
  • docs
  • internal
  • pkg
  • screenshots
  • scripts
  • testdata
  • tests
  • vendor
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Formatting enforced (vendor/github.com/alecthomas/chroma/v2/.editorconfig).
    Good: Environment pinned via vendor/github.com/alecthomas/chroma/v2/Dockerfile.
    Good: Security policy present.
  • .gitattributes
  • .gitignore
  • .goreleaser.yaml
  • .skill-loop-progress.md
  • .ubsignore
  • AGENTS.md
  • CHANGELOG.md
  • codecov.yml
  • flake.lock
  • flake.nix
  • gh_og_share_image.png
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • install.ps1
  • install.sh
  • LICENSE
    Good: Licensed under Other.
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SKILL.md
  • UPGRADE_LOG.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/dicklesworthstone/beads_viewer)](https://www.repo-grade.com/report/dicklesworthstone/beads_viewer)

More graded Go repos