Read 2026-10-04
meshtastic/firmware: technical due diligence, read from its repository
What Borehole read in meshtastic/firmware's code and history at 09e5146: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
AGENTS.md:61: states a policy on AI-generated contributions.gitmodules:1: 2 submodule(s) this survey does not read: protobufs, meshtestic
Architecture & Codebase — including AI provenance
strongsrc/mesh/NodeDB.cpp is 4,890 lines, 65× this codebase's median file
adequateThe median source file here is 75 lines. 34 files exceed 1,000 lines, the largest being 4,890. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
src/mesh/NodeDB.cpp:1 — 4,890 lines (65× median) |
src/graphics/draw/MenuHandler.cpp:1 — 3,364 lines (44× median) |
src/platform/nrf52/softdevice/ble_gap.h:1 — 2,896 lines (38× median) |
src/graphics/niche/InkHUD/Applets/System/Menu/MenuApplet.cpp:1 — 2,771 lines (36× median) |
src/platform/stm32wl/littlefs/lfs.c:1 — 2,526 lines (33× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate99 test files against 1,518 source files (6.5%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 99 test files / 1,518 source files |
Product & Engineering Maturity
adequate10% of bug fixes add or change a test
adequateOf 748 fixes in the last 24 months, 75 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 75 of 748 |
Security & Reliability Posture
adequate2 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
.clusterfuzzlite/Dockerfile — runs as root |
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate20 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/build_debian_src.yml:52 — action pinned by tag |
.github/workflows/build_firmware.yml:32 — action pinned by tag |
15 advisories against this project in the last 24 months, 7 high or critical
adequateThe newest was published on 2026-07-09. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 14 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.2.47. Answer lives in: the release you run, set against each fixed version. GHSA-95pq-gj5v-4fg2 (critical) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: its keyword search for 'firmware' is too broad to read whole (6,635 records); NVD: 1542 records name firmware with nothing tying them to this repository (CVE-1999-1548, CVE-2001-0888, CVE-2002-1067, …).
| 2026-07-09: GHSA-7ph5-2mjv-69h8 (high): Malformed encoding in User.long_name broadcast over LoRa causes client decode failure |
| 2026-04-20: GHSA-mjx5-98jq-q736 (critical): Arbitrary Code Execution via pull_request_target Fork Checkout in CI Workflow |
| 2026-01-27: GHSA-45vg-3f35-7ch2 (high): An attacker can spoof licensed amateur flag for a node |
| 2025-12-29: GHSA-377p-prwp-4hwf (moderate), fixed in 2.7.15: Forged DMs with no PKC show up as encrypted |
| 2025-08-16: GHSA-95pq-gj5v-4fg2 (critical), fixed in v2.6.3: Crafting of specific NodeInfo packets overwrite any publicKey saved in the NodeDB |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| C source is not searched: C programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on meshtastic/firmware: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.