OpenRemap
The open-source ECU binary intelligence layer — identify firmware, health-check it, verify its checksums, diff a tune into a portable recipe, and apply it to another binary of the same family.
Offline-first. No accounts, no telemetry, no data leaves your machine.
🌐 openremap.com — full documentation, wiki, and changelog.
Where the project is going (short-term roadmap)
0.7.x (current): stabilise the 0.7.0 release — fix bugs that surface in real use, and integrate third-party open-source libraries (ported with credit — never copy-paste, see THIRD_PARTY.md). This is a stability cycle, not a feature cycle.
Upcoming milestones:
- 0.8.0 — cross-firmware experiment: learn a tune from one software revision and relocate it to another by structural map matching, plus community plugin tooling.
- 0.9.0 — a refined, modern TUI.
- 1.0.0 — OpenRemap Harness: a desktop app for Windows / macOS / Linux.
Quick start
pip install openremap # or: uv tool install openremap
openremap identify stock.bin # what is this ECU? (family, SW, confidence)
openremap health stock.bin # is the file sane? (checksums, maps, VINs)
openremap cook stock.bin tuned.bin --output stage1.remap # diff → recipe
openremap cook-volatile stockA.bin stage1.bin --output portable.remap # car-portable recipe
openremap tune target.bin stage1.remap --output tuned.bin # apply → verify
Runs entirely offline. .bin, .ori, and .hex files are all accepted.
What it is
- Identify — 35 extractors across 6 OEMs (Bosch, Siemens, Delphi, Magneti Marelli, Denso, Hitachi), each result with a confidence tier and the evidence behind it
- Health-check — one command: checksums, axis sanity, map-count envelope, erased blocks, VIN duplication (CI-gateable)
- Checksums — verifies ME7, IronFelix, NefMoto, MS43, GS20/SMG2 and Denso Subaru schemes (detection only, no correction)
- Cook / tune — diff stock vs tuned into a portable
.remaprecipe (schema 4.5, map-annotated;cook-volatileexcludes VIN/checksum-store bytes with evidence for cross-car portability), apply with validate-before → apply → verify-after; merge recipes; audit the receipt - Map tooling — structural map discovery, map-level diffing, CSV export, probabilistic labels
- Library-first — every service is importable Python (identity, patching, map scanning) with a mandatory Rust core for the hot loops
Supported ECUs
6 manufacturers, 35 extractors — from LH-Jetronic (1982) to EDC17 and Denso/Hitachi Subaru (2020s). → Per-family reference
Documentation
The wiki is organised by domain:
- Getting started — install, quick start, CLI, TUI
- Concepts — how it works, confidence, evidence, recipe format
- Commands — every command, simple + advanced
- Manufacturers — per-OEM, per-family pages
Contributing
See CONTRIBUTING.md — extractor guides, code style, PR process.
Changes are tracked per version in changelog/.
License
Metadata
Release files for openremap 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| openremap-0.7.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| openremap-0.7.0-cp310-abi3-musllinux_1_2_x86_64.whl | CPython 3.10 | abi3 | Linux musl 1.2+ x86-64 | Details |
| openremap-0.7.0-cp310-abi3-manylinux_2_34_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.34+ x86-64 | Details |
| openremap-0.7.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 3.2 MB
Release files / openremap-0.7.0-cp310-abi3-win_amd64.whl
| Download URL | openremap-0.7.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 703.5 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
10780f2ce03b05ac9474bb8526860fb343933e1e346fd9da23d4aeb4bdad1532
|
|
BLAKE2b-256 checksum How to use checksums |
2ca74925687d860892a9d4921fea1f47e5afc2076e82b8185138675e4af1240e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / openremap-0.7.0-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | openremap-0.7.0-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 899.8 kB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0cd9e726dd2c6e0e6e6a599271408ce207d5468e73d2e83e77d760523f495147
|
|
BLAKE2b-256 checksum How to use checksums |
c53002b9bdde6dfb346d817883de665264a8d8f1b9be1b5e80a5e7d4e4bb1bd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / openremap-0.7.0-cp310-abi3-manylinux_2_34_x86_64.whl
| Download URL | openremap-0.7.0-cp310-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 813.0 kB |
| Tags | CPython 3.10 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c08a374bf4326e6c90006716046903ad46e76dd6faaf5d63de2237893937d666
|
|
BLAKE2b-256 checksum How to use checksums |
8e13edad590a719a4e0230b661f453856d3ff8b095f5ea9e2ff77a716b6821fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency logRelease files / openremap-0.7.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | openremap-0.7.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 784.7 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9852662faa5eab877958feae0b7a20d11764614eb4cf583131fd92bb91dc8bab
|
|
BLAKE2b-256 checksum How to use checksums |
d144dfc383d2d95d247c19748a66bd12139f2fe181911c7fbf5504514b1cef5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.
Transparency log