84

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 24% of 5,156 graded repos

Top fixes

Highest-impact changes first, ranked by point weight

7 to address
  1. 1
    README12pt

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

  2. 2
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

  3. 3
    Issue and PR templates6pt

    Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

  4. 4
    Issue and PR templates6pt

    A SECURITY.md explains how to responsibly disclose vulnerabilities. Worth adding once the project has real users.

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

81

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.

README12pt90

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

85

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.

Reproducibility6pt80

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

Tests18pt100

Test files detected (apps/aether-gateway/src/control/tests).

CI/CD14pt100

CI is configured (.github/workflows/build-tunnel.yml).

Linting and formatting5pt100

Rust linting configured (frontend/eslint.config.js, cargo clippy in CI, cargo fmt in CI).

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

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)
  • 179
    Forks
  • 93
    Releaseslatest 6mo ago

Community

  • 28% - Weak
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 1,254
    Watchers

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 43
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/build-tunnel.yml).
  • apps
    Good: Test files detected (apps/aether-gateway/src/control/tests).
  • crates
  • docs
  • frontend
    Good: Rust linting configured (frontend/eslint.config.js, cargo clippy in CI, cargo fmt in CI).
  • tools
  • .dockerignore
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • .mise.toml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • deploy.sh
  • docker-compose.local.yml
  • docker-compose.release-local.yml
  • docker-compose.single-node.yml
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • Dockerfile.app
  • Dockerfile.app.local
  • Dockerfile.app.release-local
  • generate_keys.sh
  • install.sh
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • package-lock.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.
    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.
  • rust-toolchain.toml
  • update.sh
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/fawney19/aether)](https://www.repo-grade.com/report/fawney19/aether)

More graded Rust repos