Back to matrix

E03-MT: Yes

Rationale

The pinned public Meshtastic firmware and native Portduino implementation cover the selected source-level composition under open-source licenses. The earlier 63-package inventory is now reconciled with 49 declared library.properties dependency edges: each maps to an inventoried package or the native display-library exclusion; CH341/libusb and the pinned LGPL WiFi submodule are accounted for separately. The source exposes a headless configuration without disabling PKI: MESHTASTIC_EXCLUDE_SCREEN forces HAS_SCREEN to zero, leaving niche graphics undefined excludes MessageStore, and MESHTASTIC_EXCLUDE_STOREFORWARD excludes that module. The earlier source reviews identify native real-LoRa routing, PKI/STRICT, local admission controls, independent MAC/state contexts and host-backed VFS. Firmware GPL, Portduino LGPL, platform Apache and the inspected MIT/BSD/GPL/LGPL library sources provide an open implementation candidate rather than just a specification or partial demo. A new firmware build or RF experiment is not a prerequisite of this source-availability criterion.

Assessment method

Documentary source and dependency-closure assessment; no firmware compilation or RF execution

Source context

Pinned Meshtastic/Portduino implementation, dependency manifests and license notices; reviewed 2026-10-15

Outstanding qualification

Yes concerns availability of the open-source implementation, not successful execution of every configured behavior. Keep the selected headless F16 variant explicit: exclude screen and store-forward, disable message persistence, leave niche graphics and global minimize/PKI exclusions undefined. Preserve private-channel/STRICT and local KNOWN_ONLY/key provisioning for that separate witness; ordinary CLIENT/ALL remains the C04 scope. The 49-edge reconciliation covers declared library metadata, not every conditional include or an independently certified SBOM. Host libraries and build tools remain necessary; no new claim of a frozen reproducible build, license-compliance certification, independent interoperability, benchmark or real-radio qualification is made. Existing per-cell runtime acceptance tests, including revocation cutover and volatile VFS checks, remain outstanding.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.