rust-lang/rust

0

/ 100

Documentation69
Engineering93
Health86
Rust114,255Apache-2.0today
Grade a repo

Industry-defining adoption. A few engineering gaps, but the community carries it.

Empowering everyone to build reliable and efficient software.

Documentation

69

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt58

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

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

README12pt75

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

License6pt100

Licensed under Apache-2.0.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt85

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

Tests18pt100

Test files detected (compiler/rustc_codegen_gcc/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

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

  • 1595 / 7165
    Commits (30d / 90d)
  • 15,008
    Forks
  • 150
    Releaseslatest 12y ago

Community

  • 87% - Good
    Community health
  • 12 bus factor
    authors own >50% of commits
  • 114,255
    Watchers

Responsiveness

  • 218d 6h
    Median issue response
  • <1h
    Median PR merge time
  • 12,563
    Open issues
Repository files31 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • compiler
    Good: Test files detected (compiler/rustc_codegen_gcc/tests).
  • library
    Good: Licensed under Apache-2.0.
    Good: Environment pinned via library/compiler-builtins/ci/docker/aarch64-unknown-linux-gnu/Dockerfile.
  • LICENSES
  • src
    Good: Security policy present.
  • tests
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .ignore
  • .mailmap
  • bootstrap.example.toml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • configure
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • COPYRIGHT
  • INSTALL.md
  • LICENSE-APACHE
  • license-metadata.json
  • LICENSE-MIT
  • 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.
    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.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • RELEASES.md
  • REUSE.toml
  • rust-bors.toml
  • rustfmt.toml