/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

commaai/openpilot

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:41:13.238Z

3mo ago

commaai/openpilot

commaai/openpilot is a large, active MIT-licensed open source driver-assistance platform that describes itself as an operating system for robotics and says it currently supports 300+ cars. It has very high adoption signals, with 60,453 stars and 10,758 forks, and recent commits show ongoing development through March 30, 2026.

Loading tags...

Stars60,453

Forks10,758

Default branchmaster

Last pushed2026-03-30T09:34:05Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a more customized, localized openpilot experience and can tolerate divergence from upstream. Avoid it if you want the newest upstream fixes, the standard release/staging/nightly workflow, or the lowest-maintenance path.

Choose FrogPilot if you want a more customizable, community-driven openpilot fork and are comfortable with significant divergence from upstream. Choose upstream if you want the newest fixes, cleaner maintenance, and the lowest-risk path.

Choose this fork if you want a customized, Toyota-centric openpilot with extra tuning and configuration controls and you do not need comma 3X. Choose upstream if you want broader hardware support, newer fixes, and a more standard deployment path.

Choose this fork only if you specifically need its custom vehicle support or legacy behavior. For most adopters, upstream openpilot is the safer and more maintainable choice.

Choose this fork if you want a focused openpilot derivative centered on ALC/ACC and can live with reduced breadth and heavier divergence. Choose upstream if you want the widest car support, fastest feature flow, and the least integration risk.

Choose this fork only if you need its custom branch behavior or vehicle-specific modifications. If you want current upstream fixes, active maintenance, and lower integration risk, upstream is the better default.

Prefer this fork only if you specifically want its custom tuning and legacy behavior. If you care about current car support, active maintenance, or upstream safety and tooling improvements, upstream openpilot is the better choice.

Choose this fork if you want a specialized, deeply modified openpilot branch and are willing to manage divergence. Prefer upstream if you want the newest supported behavior, easier maintenance, and clearer compatibility.

Choose this fork if you drive Subaru and want a community branch with Subaru-focused support; choose upstream if you want the latest broadly maintained openpilot features and fixes.

Choose this fork if you need a customized openpilot derivative with its own deployment and UI/tooling stack. Choose upstream if you want the broadest support, the fastest flow of new fixes, and the least merge risk.

Fork comparison

dragonpilot/dragonpilot

70/100

active

significant_divergence

Choose this fork if you want a more customized, localized openpilot experience and can tolerate divergence from upstream. Avoid it if you want the newest upstream fixes, the standard release/staging/nightly workflow, or the lowest-maintenance path.

Likely purpose

Provide an openpilot-based driver-assistance fork with additional localization, prebuilt usability, and fork-specific feature/behavior tuning for a distinct user community.

Best for

Users who want an openpilot-based fork with Chinese/community localization; Adopters who prefer prebuilt or fork-specific deployment over upstream release channels; Tinkerers who value brand-specific tuning and experimental behavior changes; People comfortable trading upstream freshness for custom features and fork identity

Additional features

Translated app and dragonpilot UI text
Pre-build branch/workflow for easier deployment
Vehicle/brand-specific tuning and initialization changes
UI polish such as improved fonts
Fork-specific behavior adjustments like DASR tuning and audio-stream handling fixes
Feature consolidation into pre/min/full packaging flow

Missing features

Falls behind upstream by about 200 commits, so it likely misses recent upstream fixes and maintenance work
Recent upstream controls, opendbc, and process replay improvements are not yet reflected here
Upstream release/staging/nightly branch cadence and its newer deployment workflow are not the fork's default path
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Actively maintained as of March 2026
Clear fork identity with localization and community-oriented changes
Large divergence suggests room for custom vehicle or workflow adaptations
Pre-build oriented branch can reduce setup friction for adopters

Risks

Large divergence from upstream makes rebasing and support harder
Being 200 commits behind upstream increases the chance of missing bugfixes and safety-related updates
Many changed files suggest higher integration and validation burden
Users relying on upstream docs or branch conventions may find the fork's workflow less familiar