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

{ Correct, Fast, Usable } -- Choose three

Documentation

70

Contributing guide5pt0

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.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

73

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.

CI/CD14pt57

CI is configured (.github/workflows/build_release_artifacts.yaml).

Reproducibility6pt80

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

Tests18pt100

Test files detected (bazel/release/homebrew/tests).

Linting and formatting5pt100

Rust linting configured (.editorconfig).

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)
  • 43
    Forks
  • 147
    Releaseslatest 3y ago

Community

  • Community health
  • authors own >50% of commits
  • 158
    Watchers

Responsiveness

  • 24d 4h
    Median issue response
  • 16h
    Median PR merge time
  • 27
    Open issues
Repository files32 root entries
  • .aspect
  • .buildkite
  • .circleci
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/build_release_artifacts.yaml).
  • .vscode
  • bazel
    Good: Test files detected (bazel/release/homebrew/tests).
  • crates
  • docs
  • examples
  • exclude
  • tools
  • .bazelignore
  • .bazelrc
  • .bazelversion
  • .editorconfig
    Good: Rust linting configured (.editorconfig).
  • .envrc
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
  • .shellcheckrc
  • BUILD.bazel
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CLAUDE.md
  • DEVELOPMENT.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • MODULE.aspect
  • MODULE.bazel
  • MODULE.bazel.lock
  • 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.
  • rustfmt.toml