keystonehq/keystone3-firmware
Grade a repo

84

/ 100

GradeB

Well engineered. The main gaps are CI and the README.

Top 24% of 5,156 graded repos

The best open source hardware wallet

Documentation82
Engineering78
Health100
C223Other6d ago

Top fixes

Highest-impact changes first, ranked by point weight

10 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
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

82

README12pt70

README is present.

Contributing guide5pt77

CONTRIBUTING guide found.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/rust-aptos-checks.yml).

Tests18pt80

Test files detected (external/lvgl/tests).

Reproducibility6pt80

Lockfile present (requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (external/lvgl/.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

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

  • 4 / 154
    Commits (30d / 90d)
  • 89
    Forks
  • 53
    Releaseslatest 1y ago

Community

  • 50% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 223
    Watchers

Responsiveness

  • 7h
    Median issue response
  • <1h
    Median PR merge time
  • 119
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/rust-aptos-checks.yml).
    Good: Issue or PR templates present.
  • docs
  • external
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: Test files detected (external/lvgl/tests).
    Good: Linter or formatter configured (external/lvgl/.editorconfig).
    Good: Security policy present.
  • hardware
  • images
  • lv_img_converter
  • rust
  • src
  • test
  • tools
  • ui_simulator
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .lldbinit
  • astyle.sh
  • build.bat
  • build.py
  • build.sh
  • CHANGELOG-BTC.md
  • CHANGELOG-ZH-BTC.md
  • CHANGELOG-ZH.md
  • CHANGELOG.md
  • CMakeLists.txt
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • entitlements.plist
  • firmware.cmake
  • img_converter.py
  • keystone3-firmware-release
  • LICENSE
    Good: Licensed under Other.
  • mh1903b.ld
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • rust-toolchain
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/keystonehq/keystone3-firmware)](https://www.repo-grade.com/report/keystonehq/keystone3-firmware)

More graded C repos