A well-known project done right. Strong docs and solid engineering throughout.

A unified toolchain for web development

Documentation

96

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

92

Reproducibility6pt70

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

CI/CD14pt85

CI is configured (.github/workflows/cargo-publish.yml).

Tests18pt100

Test files detected (crates/pack-tests/tests).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt75

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 118
    Forks
  • 554
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 15d 24h
    Median issue response
  • 4h
    Median PR merge time
  • 85
    Open issues
Repository files31 root entries
  • .agents
  • .cargo
  • .claude
  • .codex
  • .github
    Good: CI is configured (.github/workflows/cargo-publish.yml).
    Good: Issue or PR templates present.
  • .husky
  • .vscode
  • agents
  • bench
  • crates
    Good: Test files detected (crates/pack-tests/tests).
    Issue: Build artifacts or local files may be committed (crates/pack-tests/tests/snapshot/async_chunk/input/node_modules/bar) (−40 pts).Fix: Remove them and add to .gitignore.
  • e2e
  • examples
  • packages
  • scripts
  • vendor
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .typos.toml
  • AGENTS.md
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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 MIT.
  • next.js
  • package.json
  • 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.
  • rust-toolchain.toml
  • tombi.toml
  • turbo.json