95

/ 100

GradeA

Excellent work. The main thing left to polish is a contributing guide.

Top 6% of 5,156 graded repos

Burn is a next generation tensor library and Deep Learning Framework that doesn't compromise on flexibility, efficiency and portability.

Rust16,004Apache-2.09d ago

Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

8 to address
  1. 1
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  2. 2
    Install and run instructions9pt

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

  3. 3
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  4. 4
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

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

92

Contributing guide5pt67

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

94

CI/CD14pt85

CI is configured (.github/workflows/test-gpu.yml).

Reproducibility6pt90

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

Tests18pt100

Test files detected (crates/burn-backend-tests/tests).

Linting and formatting5pt100

Rust linting configured (burn-book/.prettierrc.json).

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

  • 204 / 479
    Commits (30d / 90d)
  • 1,073
    Forks
  • 42
    Releaseslatest 2y ago

Community

  • 75% - Good
    Community health
  • -
    authors own >50% of commits
  • 16,004
    Watchers

Responsiveness

  • 3d 22h
    Median issue response
  • <1h
    Median PR merge time
  • 210
    Open issues
Repository files25 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/test-gpu.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, cargo). Dependencies stay current.
    Good: Issue or PR templates present.
  • assets
  • burn-book
    Good: Rust linting configured (burn-book/.prettierrc.json).
  • contributor-book
  • crates
    Good: Test files detected (crates/burn-backend-tests/tests).
  • docs
  • examples
  • xtask
  • _typos.toml
  • .gitignore
    Good: .gitignore present.
  • benchmarks.toml
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • CITATION.cff
  • CODE-OF-CONDUCT.md
  • codecov.yml
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    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).
    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.
  • deny.toml
  • LICENSE-APACHE
  • LICENSE-MIT
  • NOTICES.md
  • POEM.md
  • 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
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/tracel-ai/burn)](https://www.repo-grade.com/report/tracel-ai/burn)

More graded Rust repos