77
/ 100
Good shape overall. A few tweaks would push it into the top tier.
{ Correct, Fast, Usable } -- Choose three
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
70
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.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
73
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 is configured (.github/workflows/build_release_artifacts.yaml).
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (bazel/release/homebrew/tests).
Rust linting configured (.editorconfig).
Project health
100
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 43Forks
- 152Releaseslatest 3y ago
Community
- 62% - FairCommunity health
- -authors own >50% of commits
- 158Watchers
Responsiveness
- 24d 4hMedian issue response
- 16hMedian PR merge time
- 27Open issues
Repository files32 root entries
- .aspect
- .buildkite
- .circleci
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/build_release_artifacts.yaml).
- .vscode
- bazelGood: Test files detected (bazel/release/homebrew/tests).
- crates
- docs
- examples
- exclude
- tools
- .bazelignore
- .bazelrc
- .bazelversion
- .editorconfigGood: Rust linting configured (.editorconfig).
- .envrc
- .gitattributes
- .gitignoreGood: .gitignore present.
- .gitlab-ci.yml
- .shellcheckrc
- BUILD.bazel
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- DEVELOPMENT.md
- LICENSEGood: Licensed under Apache-2.0.
- MODULE.aspect
- MODULE.bazel
- MODULE.bazel.lock
- README.mdGood: 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
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/aspect-build/aspect-cli)