lsusb

--lsusbv1.0.0

Converts `lsusb` command output to JSON

Linuxcommand

$ lsusb | jc-rs --lsusb

A real pair

From the reference corpus (centos-7.7/lsusb.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

lsusbcentos-7.7

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

expected outputjson

[
  {
    "bus": "001",
    "device": "001",
    "id": "1d6b:0002",
    "description": "Linux Foundation 2.0 root hub"
  },
  {
    "bus": "002",
    "device": "004",
    "id": "0e0f:0008",
    "description": "VMware, Inc."
  },
  {
    "bus": "002",
    "device": "003",
    "id": "0e0f:0002",
    "description": "VMware, Inc. Virtual USB Hub"
  },
  {
    "bus": "002",
    "device": "002",
    "id": "0e0f:0003",
    "description": "VMware, Inc. Virtual Mouse"
  },
  {
    "bus": "002",
    "device": "001",
    "id": "1d6b:0001",
    "description": "Linux Foundation 1.1 root hub"
  }
]

Fixture coverage

9/9oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs lsusbjc-rs runs the command itself and parses what it prints. Recognised for: `lsusb`

Source: crates/jc-rs-parsers/src/system/lsusb.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare