94

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide. It just hasn't found an audience yet.

Top 6% of 5,156 graded repos

Henad is a very fast parallel agent-based modelling engine that runs on both CPU and GPU, native and in-browser via WASM on WebGPU. (>10,000x faster than NetLogo!)

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

12 to address
  1. 1
    Install and run instructions9pt

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

  2. 2
    Reproducibility6pt

    Ensure .github/dependabot.yml lists 2+ package-ecosystem entries (e.g. your language plus github-actions).

  3. 3
    Dependency manifest6pt

    Add a [project.urls] table (Homepage, Repository) so PyPI links back to your project.

  4. 4
    Dependency manifest6pt

    Add `authors = [...]` under [project] so the package has clear ownership.

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

90

Contributing guide5pt53

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 instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

99

Reproducibility6pt92

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

Tests18pt100

Test files detected (crates/henad-build/src/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

93

Dependency manifest6pt79

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)
  • 0
    Forks
  • 3
    Releaseslatest 21d ago

Community

  • 71% - Fair
    Community health
  • -
    authors own >50% of commits
  • 3
    Watchers

Responsiveness

  • 3d 1h
    Median issue response
  • <1h
    Median PR merge time
  • 6
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • assets
  • benchmarks
  • crates
    Good: Test files detected (crates/henad-build/src/tests).
  • docs
    Good: Licensed under Apache-2.0.
  • examples
  • scripts
    Good: Environment pinned via scripts/.python-version.
  • templates
    Good: Dependabot is configured. Dependencies update automatically.
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .typos.toml
  • about.hbs
  • about.toml
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • check.sh
  • clippy.toml
  • 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.
    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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • deny.toml
  • index.html
  • LICENSE-APACHE
  • LICENSE-MIT
  • pyproject.toml
  • 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.
  • ROADMAP.md
  • rust-toolchain
  • rustfmt.toml
    Good: Linter or formatter configured (rustfmt.toml).
  • Trunk.toml
  • uv.lock
  • vercel.json
  • zensical.toml
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/micfong-z/henad)](https://www.repo-grade.com/report/micfong-z/henad)

More graded Rust repos