Location: cmd/cantool/main.go:122
Finding: The capabilities command reports "features": ["fd", "xl"]. RELAY's feature-string vocabulary for CAN (spec §12.2) defines "fd", "isotp", "j1939", "uds", and "obdii". The binary actually ships fully-implemented isotp, j1939, uds, and obdii packages, but none of the corresponding feature strings are reported, so relay capabilities/compare/report under-report what the tool can actually do. Separately, "xl" isn't one of the spec-defined feature values (unknown values are tolerated by the spec but ignored by conformant tooling), so it doesn't help either.
Recommendation: Emit ["fd", "isotp", "j1939", "uds", "obdii"] (plus whatever value the project agrees on for CAN XL support), and ideally derive the list from build-time reality rather than a hand-maintained literal so it can't drift again.
Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.
Location:
cmd/cantool/main.go:122Finding: The
capabilitiescommand reports"features": ["fd", "xl"]. RELAY's feature-string vocabulary for CAN (spec §12.2) defines"fd","isotp","j1939","uds", and"obdii". The binary actually ships fully-implementedisotp,j1939,uds, andobdiipackages, but none of the corresponding feature strings are reported, sorelay capabilities/compare/reportunder-report what the tool can actually do. Separately,"xl"isn't one of the spec-defined feature values (unknown values are tolerated by the spec but ignored by conformant tooling), so it doesn't help either.Recommendation: Emit
["fd", "isotp", "j1939", "uds", "obdii"](plus whatever value the project agrees on for CAN XL support), and ideally derive the list from build-time reality rather than a hand-maintained literal so it can't drift again.Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.