com-lihaoyi/mill

0

/ 100

Documentation47
Engineering82
Health100
Scala2,756MIT1d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

A better build tool for Java, Scala and Kotlin: Simpler than Maven, easier than Gradle, with 3-7x faster dev workflows than other JVM build tools

Documentation

47

Contributing guide5pt5

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt40

README is present.

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt100

Licensed under MIT.

Engineering

82

CI/CD14pt72

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

Tests18pt80

Test files detected (contrib/buildinfo/test).

Reproducibility6pt82

Lockfile present (example/pythonlib/dependencies/2-pip-requirements/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (contrib/sbom/test/reference/pom.xml).

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)
  • 440
    Forks
  • 158
    Releaseslatest 8y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,756
    Watchers

Responsiveness

  • 3d 23h
    Median issue response
  • 11h
    Median PR merge time
  • 237
    Open issues
Repository files33 root entries
  • .codex
  • .github
    Good: CI is configured (.github/workflows/draft-ci.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • ci
  • contrib
    Good: Test files detected (contrib/buildinfo/test).
    Good: Dependency manifest found (contrib/sbom/test/reference/pom.xml).
  • core
  • dist
  • example
    Good: Lockfile present (example/pythonlib/dependencies/2-pip-requirements/requirements.txt). Installs are reproducible.
  • integration
  • libs
  • mill-build
  • runner
  • scratch
  • testkit
  • website
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mill-jvm-version
  • .scalafix.conf
  • .scalafmt.conf
  • AGENTS.md
  • build.mill
  • changelog.adoc
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • default-mill-jvm-version
  • developer.adoc
  • LICENSE
    Good: Licensed under MIT.
  • mill
  • mill.bat
  • profile.png
  • readme.adoc
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.