blockstream/green_qt
Grade a repo

0

/ 100

GradeF

Early-stage engineering. The fastest wins are setup instructions and the README.

Higher than 42% of 5,156 graded repos

Blockstream Green App

Documentation36
Engineering71
Health62
C++262GPL-3.021d ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (77).

See your top fixes
Now
F
58
Potential
C
77

Top fixes

Highest-impact changes first, ranked by point weight

15 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

    Expand with a description, install steps, usage, and examples.

  3. 3
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  4. 4
    README12pt

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

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

36

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt45

README is present.

License6pt100

Licensed under GPL-3.0.

Engineering

71

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt10

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Tests18pt80

Test files detected (doc/tests).

CI/CD14pt100

CI is configured (.gitlab-ci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

62

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 10 / 125
    Commits (30d / 90d)
  • 44
    Forks
  • 98
    Releaseslatest 6y ago

Community

  • 50% - Fair
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 262
    Watchers

Responsiveness

  • 4d 15h
    Median issue response
  • -
    Median PR merge time
  • 26
    Open issues
Repository files32 root entries
  • .github
    Good: Issue or PR templates present.
  • .gitlab
  • assets
  • ci
    Good: Environment pinned via ci/codesigntool/Dockerfile.
  • cmake
  • doc
    Good: Test files detected (doc/tests).
  • i18n
  • qml
  • src
  • tests
  • tools
    Issue: Build artifacts or local files may be committed (tools/staging/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitlab-ci.yml
    Good: CI is configured (.gitlab-ci.yml).
  • .qmllint.ini
  • AGENTS.md
  • ARCHITECTURE.md
  • blockstream.desktop
  • build.bat
  • CHANGELOG.md
  • CMakeLists.txt
  • CMakePresets.json
  • commitlint.config.js
  • entitlements_debug.plist
  • entitlements.plist
  • Info.plist.in
  • installer.iss.in
  • LICENSE
    Good: Licensed under GPL-3.0.
  • production.rc
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
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/blockstream/green_qt)](https://www.repo-grade.com/report/blockstream/green_qt)

More graded C++ repos