opentensor/subtensor
Grade a repo

0

/ 100

GradeA

Polished and well engineered. Punching above its star count.

Top 12% of 5,156 graded repos

Bittensor Blockchain Layer

Documentation92
Engineering86
Health97
Rust353Unlicense1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

14 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

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 Unlicense.

Engineering

86

Tests18pt80

Test files detected (contract-tests/test).

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/check-bittensor-e2e-tests.yml).

Linting and formatting5pt100

Rust linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

97

Dependency manifest6pt90

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

  • -
    Commits (30d / 90d)
  • 317
    Forks
  • 85
    Releaseslatest 1y ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 353
    Watchers

Responsiveness

  • 19d 22h
    Median issue response
  • 1d 22h
    Median PR merge time
  • 417
    Open issues
Repository files43 root entries
  • .agents
  • .claude
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/check-bittensor-e2e-tests.yml).
    Good: Issue or PR templates present.
  • .maintain
  • .vscode
  • chain-extensions
  • chainspecs
  • common
  • contract-tests
    Good: Test files detected (contract-tests/test).
  • docs
  • eco-tests
  • node
  • pallets
  • precompiles
  • primitives
  • runtime
  • scripts
  • src
  • support
  • ts-tests
  • .dockerignore
  • .editorconfig
    Good: Rust linting configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .rustfmt.toml
  • build.rs
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • 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.
  • docker-compose.localnet.yml
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Dockerfile-localnet
  • hyperparameters.md
  • justfile
  • LICENSE
    Good: Licensed under Unlicense.
  • 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.
  • recipe.json
  • rust-toolchain.toml
  • rustfmt.toml
  • shell.nix
  • 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