chaitin/agent-compose
Grade a repo

0

/ 100

GradeB

Impressive early momentum. Already polished and picking up traction fast.

Top 16% of 5,156 graded repos
Documentation86
Engineering94
Health76
Go157AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 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 a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

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

README12pt70

README is present.

Contributing guide5pt82

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

94

CI/CD14pt85

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

Reproducibility6pt85

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

Tests18pt100

Test files detected (cmd/agent-compose/e2e_docker_scheduler_test.go).

Linting and formatting5pt100

Formatting enforced (gofmt (built into Go toolchain)).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

76

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt75

Dependency manifest found (go.mod).

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)
  • 14
    Forks
  • 3
    Releaseslatest 1mo ago

Community

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

Responsiveness

  • 3d 9h
    Median issue response
  • 3h
    Median PR merge time
  • 29
    Open issues
Repository files37 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • agent-script
  • assets
  • cmd
    Good: Test files detected (cmd/agent-compose/e2e_docker_scheduler_test.go).
  • deploy
  • docs
  • examples
  • frontend
  • guest-images
  • loader-script
  • nginx
  • pkg
  • playground
  • proto
  • runtime
  • scripts
  • test
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • build_docker.sh
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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.
    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.
  • docker-compose.deploy.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile.agent-compose-local
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE.txt
    Good: Licensed under AGPL-3.0.
  • package-lock.json
  • package.json
  • 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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • Taskfile.yml
  • TESTING.md
  • tsconfig.json
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/chaitin/agent-compose)](https://www.repo-grade.com/report/chaitin/agent-compose)

More graded Go repos