Monthly check that the compatibility list still matches what the
vendors are publishing. Nothing here is automated on purpose:
deciding whether an advisory changed in a way that matters is the
part that needs reading.
data/devices.json was last marked updated 2026-08-16 — 8 days ago.
Currently tracking 20 entries across
19 vendors.
Re-check each advisory
What to look for
- A model moving off the "no OAuth firmware" list — that is the
single most valuable change to catch, because
NO-OAUTH-FIRMWARE.md
tells people their hardware is a write-off.
- New models added to an existing advisory.
- A vendor publishing an advisory for the first time — those are
new rows, and the reason to keep doing this.
- A dead link. An entry whose evidence URL 404s cannot be checked
by a reader and should be replaced or removed.
When something changed
- Edit
data/devices.json and
bump its updated field.
- Run
python tools/build-device-table.py to regenerate the
docs table. CI fails if you skip it.
Close this issue when the pass is done, even if nothing changed —
that is a useful signal too.
Monthly check that the compatibility list still matches what the
vendors are publishing. Nothing here is automated on purpose:
deciding whether an advisory changed in a way that matters is the
part that needs reading.
data/devices.json was last marked updated 2026-08-16 — 8 days ago.
Currently tracking 20 entries across
19 vendors.
Re-check each advisory
check-advisory— advisoryunsupported— advisorycheck-advisory— advisory (unverified (403) from CI — check by hand)check-advisory— advisorycheck-advisory— advisorypartial— advisorynone-planned— advisorycheck-advisory— advisorycheck-advisory— advisorycheck-advisory— advisorycheck-advisory— advisoryavailable, partial— advisory · advisoryunsupported— advisorycheck-advisory— advisorypartial— advisorycheck-advisory— advisorycheck-advisory— advisorypartial— advisorypartial— advisoryWhat to look for
single most valuable change to catch, because
NO-OAUTH-FIRMWARE.md
tells people their hardware is a write-off.
new rows, and the reason to keep doing this.
by a reader and should be replaced or removed.
When something changed
data/devices.jsonandbump its
updatedfield.python tools/build-device-table.pyto regenerate thedocs table. CI fails if you skip it.
Close this issue when the pass is done, even if nothing changed —
that is a useful signal too.