mosure/bevy_gaussian_splatting
Grade a repo

91

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 11% of 5,156 graded repos

bevy gaussian splatting render pipeline plugin 🕊️🌌

Documentation93
Engineering87
Health98
Rust270Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Install and run instructions9pt

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

  2. 2
    Reproducibility6pt

    Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.

  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
    Dependency manifest6pt

    Add `documentation = "https://docs.rs/<crate>"` to [package] so users can find the API docs.

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

93

Contributing guide5pt73

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

87

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.

Reproducibility6pt92

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

Tests18pt100

Test files detected (tests).

CI/CD14pt100

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

Linting and formatting5pt100

Rust linting configured (cargo clippy in CI).

Project health

98

Dependency manifest6pt95

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

  • 10 / 10
    Commits (30d / 90d)
  • 25
    Forks
  • 15
    Releaseslatest 1y ago

Community

  • 57% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 270
    Watchers

Responsiveness

  • 78d 11h
    Median issue response
  • 1d 13h
    Median PR merge time
  • 86
    Open issues
Repository files21 root entries
  • .cargo
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot configured for cargo.
  • .vscode
  • assets
  • benches
  • docs
  • examples
  • src
  • tests
    Good: Test files detected (tests).
  • tools
  • viewer
  • www
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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.
    Good: Contributing guide includes setup/install instructions.
    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.
  • LICENSE-APACHE
  • LICENSE-MIT
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
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/mosure/bevy_gaussian_splatting)](https://www.repo-grade.com/report/mosure/bevy_gaussian_splatting)

More graded Rust repos