tokuhirom/mutsu
Grade a repo

0

/ 100

GradeB

Solid engineering. The main gap is visibility.

Documentation82
Engineering80
Health84
Raku5today

Documentation

82

README12pt70

README is present.

Contributing guide5pt72

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

80

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.

Tests18pt80

Test files detected (raku-doc/doc/Type/IO/Spec).

Reproducibility6pt80

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

CI/CD14pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

84

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 manifest6pt100

Dependency manifest found (Cargo.toml).

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
  • 1
    Releaseslatest 1d ago

Community

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

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 11
    Open issues
Repository files34 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • benchmarks
  • docs
  • news
  • old-design-docs
    Good: A license file is present.
  • raku-doc
    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: Test files detected (raku-doc/doc/Type/IO/Spec).
    Good: Issue or PR templates present.
  • roast
  • scripts
  • src
  • t
  • tests
  • todo
  • TODO_roast
  • tools
  • wasm-demo
  • -
  • .gitignore
    Good: .gitignore present.
  • .mise.toml
    Good: Environment pinned via .mise.toml.
  • .tagpr
  • AGENTS.md
  • ANALYSIS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • CLAUDE.md
  • HISTORY-pass.svg
  • HISTORY.tsv
  • lefthook.yml
  • Makefile
  • mise.toml
  • PERFORMANCE.md
  • PLAN.md
  • 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.
  • roast-whitelist.txt