rlane/oort3
Grade a repo

0

/ 100

GradeD

Popular for its size, but the engineering basics lag behind the interest.

Top 48% of 5,156 graded repos

A space fleet programming game

Documentation42
Engineering73
Health100
Rust326GPL-3.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (84).

See your top fixes
Now
D
68
Potential
B
84

Top fixes

Highest-impact changes first, ranked by point weight

14 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  3. 3
    README12pt

    Add an Overview, Install, Usage, and Contributing section at minimum.

  4. 4
    README12pt

    Add more sections (Overview, Install, Usage, Contributing) using ## headings.

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

42

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.

README12pt28

README is present.

Install and run instructions9pt45

README documents how to install the project.

License6pt100

Licensed under GPL-3.0.

Engineering

73

Linting and formatting5pt0

No Rust linting or formatting enforced.

→ Add `cargo clippy -- -D warnings` and `cargo fmt --check` as CI steps, and optionally a rustfmt.toml for project-specific style rules.

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/CD14pt85

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

Tests18pt100

Test files detected (shared/simulator/tests).

Reproducibility6pt100

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

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)
  • 27
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 326
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 19h
    Median PR merge time
  • 7
    Open issues
Repository files23 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/check.yml).
    Good: Dependabot covers 2 ecosystems (cargo, cargo). Dependencies stay current.
  • .vim
  • assets
  • bundler
  • firebase
  • frontend
  • scripts
  • services
    Good: Environment pinned via services/backend/Dockerfile.
  • shared
    Good: Test files detected (shared/simulator/tests).
  • tools
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .watchmanconfig
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.lock.user
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • Cargo.toml.user
  • CHANGELOG.md
  • LICENSE
    Good: Licensed under GPL-3.0.
  • oort3.code-workspace
  • README.md
    Good: README is present.
    Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    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.
  • rust-toolchain.toml
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/rlane/oort3)](https://www.repo-grade.com/report/rlane/oort3)

More graded Rust repos