ajouatom/openpilot

0

/ 100

Documentation86
Engineering93
Health84
Python181MIT1d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Documentation

86

README12pt78

README is present.

Contributing guide5pt79

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

93

Reproducibility6pt80

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

CI/CD14pt85

CI is configured (.github/workflows/ci_weekly_report.yaml).

Tests18pt100

Test files detected (cereal/messaging/tests).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 173
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 181
    Watchers

Responsiveness

  • 7h
    Median issue response
  • <1h
    Median PR merge time
  • 4
    Open issues
Repository files49 root entries
  • .github
    Good: CI is configured (.github/workflows/ci_weekly_report.yaml).
    Good: Issue or PR templates present.
  • .vscode
  • apps
  • cereal
    Good: Test files detected (cereal/messaging/tests).
  • common
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • msgq_repo
  • opendbc_repo
  • openpilot
  • panda
    Good: Environment pinned via panda/Dockerfile.
  • rednose_repo
  • release
  • scripts
  • selfdrive
  • site_scons
  • system
  • teleoprtc_repo
  • third_party
  • tinygrad_repo
  • tools
  • .clang-tidy
  • .dockerignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • codecov.yml
  • conftest.py
  • Dockerfile.openpilot
  • Dockerfile.openpilot_base
  • git_src_commit
  • git_src_commit_date
  • Jenkinsfile
  • launch_chffrplus.sh
  • launch_env.sh
  • launch_openpilot.sh
  • LICENSE
    Good: Licensed under MIT.
  • mkdocs.yml
  • msgq
  • opendbc
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.md
    Good: README is present.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rednose
  • RELEASES.md
  • restart.sh
  • SConstruct
  • SECURITY.md
    Good: Security policy present.
  • teleoprtc
  • tinygrad
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.