opentensor/subtensor
Grade a repo

87

/ 100

GradeB

Well engineered. The main gaps are the repo description and topics and a contributing guide.

Top 18% of 5,156 graded repos

Bittensor

Documentation89
Engineering87
Health81
Rust394Apache-2.014d ago

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    Tests18pt

    Add test/dev tooling under [dev-dependencies] so `cargo test` runs a complete suite.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

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

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

89

Contributing guide5pt47

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

87

Tests18pt80

Test files detected (.github/scripts/test_docs_preview_artifact.py).

CI/CD14pt85

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

Reproducibility6pt92

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

Linting and formatting5pt100

Rust linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

81

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 manifest6pt90

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

  • 264 / 941
    Commits (30d / 90d)
  • 356
    Forks
  • 121
    Releaseslatest 2y ago

Community

  • 62% - Fair
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 394
    Watchers

Responsiveness

  • 19d 22h
    Median issue response
  • 1d 22h
    Median PR merge time
  • 79
    Open issues
Repository files48 root entries
  • .agents
  • .cargo
  • .claude
  • .github
    Good: Test files detected (.github/scripts/test_docs_preview_artifact.py).
    Good: CI is configured (.github/workflows/build-core-wheels.yml).
    Good: Issue or PR templates present.
  • .maintain
  • .openai
  • .vscode
  • chain-extensions
  • chainspecs
  • clones
  • common
  • docs
  • eco-tests
  • ink-contract
  • node
  • pallets
  • precompiles
  • primitives
  • runtime
  • scripts
  • sdk
  • src
  • support
  • ts-tests
  • vendor
    Good: Dependabot is configured. Dependencies update automatically.
    Good: Security policy present.
  • website
  • .dockerignore
  • .editorconfig
    Good: Rust linting configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .rustfmt.toml
  • AGENTS.md
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • ci_tips.md
  • 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.
  • Cross.toml
  • docker-compose.localnet.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile-localnet
  • Dockerfile.prebuilt
  • justfile
  • LICENSE
    Good: Licensed under Apache-2.0.
  • 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.
  • rust-toolchain.toml
  • snapshot.json
  • zepter.yaml
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/opentensor/subtensor)](https://www.repo-grade.com/report/opentensor/subtensor)

More graded Rust repos