95

/ 100

GradeA

Exemplary work. Strong across project hygiene, documentation, and engineering.

Top 6% of 5,156 graded repos

Private Monero + Tari merge mining — the whole stack in one command: full node, P2Pool, XvB optimizer, and a live dashboard, all behind Tor.

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

3 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    Install and run instructions9pt

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

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

96

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

93

Tests18pt80

Test files detected (build/dashboard/tests).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (build/dashboard/uv.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (build/dashboard/pyproject.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

  • 197 / 462
    Commits (30d / 90d)
  • 8
    Forks
  • 39
    Releaseslatest 1mo ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 33
    Watchers

Responsiveness

  • 15h
    Median issue response
  • <1h
    Median PR merge time
  • 11
    Open issues
Repository files34 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 4 ecosystems (github-actions, uv, docker, docker-compose). Dependencies stay current.
    Good: Issue or PR templates present.
  • build
    Good: Test files detected (build/dashboard/tests).
    Good: Lockfile present (build/dashboard/uv.lock). Installs are reproducible.
    Good: Environment pinned via build/dashboard/Dockerfile.
    Good: Dependency manifest found (build/dashboard/pyproject.toml).
  • docs
  • images
  • scripts
  • tests
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .hadolint.yaml
  • .lycheeignore
  • .markdownlint-cli2.jsonc
  • .pre-commit-config.yaml
  • .taplo.toml
  • .trivyignore
  • .yamllint
  • biome.json
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • config.core-keys.json
  • config.minimal.json
  • config.reference.json
  • 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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • pithead
  • pithead-completion.bash
  • 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.
  • ruff.toml
  • SECURITY.md
    Good: Security policy present.
  • THIRD_PARTY_LICENSES.md
  • VERSION
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/p2pool-starter-stack/pithead)](https://www.repo-grade.com/report/p2pool-starter-stack/pithead)

More graded Python repos