holon-run/holon
Grade a repo

0

/ 100

GradeC

Good shape overall. A few tweaks would push it into the top tier.

Top 38% of 5,156 graded repos

A local workbench for agents doing continuous work across sessions, commands, human input, and external events.

Documentation76
Engineering67
Health100
Rust125Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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
    README12pt

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

  3. 3
    Install and run instructions9pt

    Add a section showing how to start or use the project.

  4. 4
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

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

76

Install and run instructions9pt55

README documents how to install the project.

Contributing guide5pt74

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.

README12pt80

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

67

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.

Reproducibility6pt75

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

Tests18pt80

Test files detected (benchmark/tests).

CI/CD14pt100

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

Project health

100

Dependency manifest6pt100

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

  • -
    Commits (30d / 90d)
  • 11
    Forks
  • 37
    Releaseslatest 7mo ago

Community

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

Responsiveness

  • 8d 19h
    Median issue response
  • <1h
    Median PR merge time
  • 34
    Open issues
Repository files26 root entries
  • .codex
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .holon
  • benchmark
    Good: Test files detected (benchmark/tests).
  • benchmarks
  • builtin_templates
  • docs
  • e2e-manual
  • holonbot
  • scripts
  • skills
  • src
  • tests
  • web-gui
  • .gitignore
    Good: .gitignore present.
  • action.yml
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • 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.
    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.
  • 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.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • README.zh-CN.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/holon-run/holon)](https://www.repo-grade.com/report/holon-run/holon)

More graded Rust repos