trezor/trezor-firmware
Grade a repo

85

/ 100

GradeB

Well engineered. The main gaps are setup instructions and the README.

Top 22% of 5,156 graded repos

:lock: Trezor Firmware Monorepo

Documentation69
Engineering90
Health100
C1,826Other6d ago

Top fixes

Highest-impact changes first, ranked by point weight

12 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
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  3. 3
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  4. 4
    Install and run instructions9pt

    Add a section showing how to install dependencies.

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

69

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt61

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt75

README is present.

License6pt100

Licensed under Other.

Engineering

90

Tests18pt80

Test files detected (common/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/crowdin-ui-check-reuse.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (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

  • 238 / 863
    Commits (30d / 90d)
  • 802
    Forks
  • 0
    Releases

Community

  • 75% - Good
    Community health
  • 5 bus factor
    authors own >50% of commits
  • 1,826
    Watchers

Responsiveness

  • 219d 15h
    Median issue response
  • 15h
    Median PR merge time
  • 731
    Open issues
Repository files38 root entries
  • .clusterfuzzlite
    Good: Environment pinned via .clusterfuzzlite/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/crowdin-ui-check-reuse.yml).
    Good: Issue or PR templates present.
  • ci
  • common
    Good: Test files detected (common/tests).
  • core
  • crypto
  • docs
  • legacy
  • nordic
  • python
  • rust
  • storage
  • tests
  • tools
  • vendor
  • .clang-format
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pylintrc
  • .yamllint.yml
  • build-docker.sh
  • CODEOWNERS
  • COMMITS.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +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).
    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.
  • COPYING
  • create_monorepo.py
  • LICENSE.md
    Good: Licensed under Other.
  • Makefile
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pyrightconfig.json
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • setup.cfg
  • shell.nix
  • tbench.toml
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
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/trezor/trezor-firmware)](https://www.repo-grade.com/report/trezor/trezor-firmware)

More graded C repos