halbritt/striatum
Grade a repo

0

/ 100

GradeC

Solid early foundation. Docs and CI will help it get noticed.

Top 43% of 5,156 graded repos

Local-first orchestration for terminal-based AI coding agents

Documentation75
Engineering60
Health100
Go5Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

15 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

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

  4. 4
    CI/CD14pt

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

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

75

README12pt50

README is present.

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

60

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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/CD14pt72

CI is configured (.github/workflows/ci-installed-cli.yml).

Tests18pt80

Test files detected (docs/operator/artifacts/rfc-0078-closure/tests).

Reproducibility6pt80

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

Project health

100

Dependency manifest6pt100

Dependency manifest found (go/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)
  • 1
    Forks
  • 89
    Releaseslatest 3mo ago

Community

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

Responsiveness

  • 16h
    Median issue response
  • <1h
    Median PR merge time
  • 24
    Open issues
Repository files27 root entries
  • .agy
  • .github
    Good: CI is configured (.github/workflows/ci-installed-cli.yml).
  • contracts
  • docs
    Good: Test files detected (docs/operator/artifacts/rfc-0078-closure/tests).
  • dogfoods
  • examples
    Good: Environment pinned via examples/dev-postgres/docker-compose.yml.
  • go
    Good: Lockfile present (go/go.sum). Installs are reproducible.
    Good: Dependency manifest found (go/go.mod).
  • prompts
  • scripts
  • skills
  • workflows
  • .check-docs-ignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • AGENTS.md
  • ARCHITECTURE.md
  • CHANGELOG.md
  • CLAUDE.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.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • install.sh
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • 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.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
  • striatum-STRIATUM_AGENT_GUIDE.manifest.json
  • striatum-STRIATUM_AGENT_GUIDE.md
  • VERSION
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/halbritt/striatum)](https://www.repo-grade.com/report/halbritt/striatum)

More graded Go repos