Teardown Audit: What the OpenWrt One’s Source Page and Recovery Path Actually Prove About GPL Compliance
The question a teardown can answer "Does the OpenWrt One deliver GPL compliance?" is the wrong first question for a forensic auditor, because a source download page is a claim, not a finding. The device is a useful worked example precisely because it publishes more than most routers: a per-build source archive and a hardware how-to that documents serial, JTAG, and a NOR-based full recovery path. What a teardown can establish is narrower and more useful: whether the published artifacts map to the shipped firmware, whether the physical access needed to verify and exercise that firmware exists, and where the gaps are that a vendor must close. I treat the OpenWrt One here as a specimen for a repeatable audit method, not as a compliance verdict. The retrieved sources do…