jacobaraujo7/remote_pi
Grade a repo

77

/ 100

GradeB

Well engineered. The main gaps are issue and PR templates and a contributing guide.

Top 20% of 5,156 graded repos

Control your Pi coding agent from your phone. Pair with a one-time QR code and chat with your local agent, even when you're away from your computer.

Documentation89
Engineering78
Health100
Dart425MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

8 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

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

  3. 3
    Install and run instructions9pt

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

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry, or a renovate.json, so dependencies are updated automatically.

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

89

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

78

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (app/ios/RunnerTests/RunnerTests.swift).

Reproducibility6pt80

Lockfile present (cockpit/cli/Cargo.lock). Installs are reproducible.

CI/CD14pt100

CI is configured (.github/workflows/cockpit-cli.yml).

Linting and formatting5pt100

Linter or formatter configured (site/eslint.config.mjs).

Project health

100

Dependency manifest6pt100

Dependency manifest found (app/android/app/build.gradle.kts).

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

  • 108 / 724
    Commits (30d / 90d)
  • 120
    Forks
  • 109
    Releaseslatest 4mo ago

Community

  • 42% - Weak
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 425
    Watchers

Responsiveness

  • 20h
    Median issue response
  • 10h
    Median PR merge time
  • 66
    Open issues
Repository files22 root entries
  • .claude
  • .cockpit
  • .github
    Good: CI is configured (.github/workflows/cockpit-cli.yml).
  • .orchestration
  • app
    Good: Test files detected (app/ios/RunnerTests/RunnerTests.swift).
    Good: Dependency manifest found (app/android/app/build.gradle.kts).
  • branding
  • cockpit
    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: Lockfile present (cockpit/cli/Cargo.lock). Installs are reproducible.
  • pi-extension
  • plan
  • relay
    Good: Environment pinned via relay/Dockerfile.
  • review
  • rp-s3
  • scripts
  • site
    Good: Linter or formatter configured (site/eslint.config.mjs).
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CLAUDE.md
  • github-actions.panel
  • LICENSE
    Good: Licensed under MIT.
  • PROTOCOL.md
  • pull-requests.panel
  • 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.
    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.
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/jacobaraujo7/remote_pi)](https://www.repo-grade.com/report/jacobaraujo7/remote_pi)

More graded Dart repos