bevyengine/bevy
Grade a repo

90

/ 100

GradeA

A top-tier open source project. Docs, tests, and CI are all in excellent shape.

Top 12% of 5,156 graded repos

A refreshingly simple data-driven game engine built in Rust

Documentation90
Engineering86
Health100
Rust46,893Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

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

  4. 4
    Install and run instructions9pt

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

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

90

Contributing guide5pt52

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.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

86

CI/CD14pt57

CI is configured (.github/workflows/ci-comment-failures.yml).

Reproducibility6pt90

Lockfile present (.github/start-mobile-example/package-lock.json). Installs are reproducible.

Tests18pt100

Test files detected (.github/start-wasm-example/tests).

Linting and formatting5pt100

Rust linting configured (rustfmt.toml).

Issue and PR templates6pt100

Issue or PR templates present.

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

  • 142 / 749
    Commits (30d / 90d)
  • 4,662
    Forks
  • 57
    Releaseslatest 3y ago

Community

  • 100% - Good
    Community health
  • 16 bus factor
    authors own >50% of commits
  • 46,893
    Watchers

Responsiveness

  • 38d 13h
    Median issue response
  • 11h
    Median PR merge time
  • 3,277
    Open issues
Repository files29 root entries
  • _release-content
  • .cargo
  • .github
    Good: Test files detected (.github/start-wasm-example/tests).
    Good: CI is configured (.github/workflows/ci-comment-failures.yml).
    Good: Lockfile present (.github/start-mobile-example/package-lock.json). Installs are reproducible.
    Good: Dependabot covers 2 ecosystems (cargo, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: .gitignore present.
  • assets
    Good: Licensed under Apache-2.0.
  • benches
  • crates
  • docs
  • docs-rs
  • docs-template
  • errors
  • examples
  • src
  • tests
  • tests-integration
  • tools
  • .gitattributes
  • .gitignore
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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).
    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.
  • CREDITS.md
  • deny.toml
  • 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.
  • rustfmt.toml
    Good: Rust linting configured (rustfmt.toml).
  • SECURITY.md
    Good: Security policy present.
  • typos.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/bevyengine/bevy)](https://www.repo-grade.com/report/bevyengine/bevy)

More graded Rust repos