rust-lang/cargo
Grade a repo

94

/ 100

GradeA

Excellent work. The main thing left to polish is the README.

Top 10% of 5,156 graded repos

The Rust package manager

Documentation80
Engineering99
Health92
Rust15,533Apache-2.09d ago

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Make sure the Renovate config is valid JSON, for example `{ "extends": ["config:recommended"] }`.

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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

80

Contributing guide5pt60

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

99

Reproducibility6pt92

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

Tests18pt100

Test files detected (crates/cargo-platform/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

92

Dependency manifest6pt75

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

  • 132 / 614
    Commits (30d / 90d)
  • 3,061
    Forks
  • 0
    Releases

Community

  • 87% - Good
    Community health
  • 4 bus factor
    authors own >50% of commits
  • 15,533
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 4h
    Median PR merge time
  • 1,677
    Open issues
Repository files30 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/main.yml).
    Good: Renovate config present (.github/renovate.json5).
    Good: Issue or PR templates present.
  • benches
  • ci
  • crates
    Good: Test files detected (crates/cargo-platform/tests).
    Good: Environment pinned via crates/cargo-test-support/containers/apache/Dockerfile.
  • credential
  • doc
    Good: Security policy present.
  • etc
  • src
  • tests
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .ignore
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CHANGELOG.md
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • deny.toml
  • LICENSE-APACHE
  • LICENSE-MIT
  • LICENSE-THIRD-PARTY
  • publish.py
  • 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
    Good: Rust linting configured (rustfmt.toml, cargo clippy in CI, cargo fmt in CI).
  • triagebot.toml
  • typos.toml
  • windows.manifest.xml
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/rust-lang/cargo)](https://www.repo-grade.com/report/rust-lang/cargo)

More graded Rust repos