ufw-appinfo

--ufw-appinfov1.3.0

Converts `ufw app info [application]` command output to JSON

Linuxcommand

$ ufw app | jc-rs --ufw-appinfo

A real pair

From the reference corpus (generic/ufw-appinfo-msn.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.

ufw appgeneric

Profile: MSN
Title: MSN Chat
Description: MSN chat protocol (with file transfer and voice)

Ports:
  1863
  6891:6900/tcp
  6901

expected outputjson

[
  {
    "profile": "MSN",
    "title": "MSN Chat",
    "description": "MSN chat protocol (with file transfer and voice)",
    "tcp_list": [
      1863,
      6901
    ],
    "udp_list": [
      1863,
      6901
    ],
    "tcp_ranges": [
      {
        "start": 6891,
        "end": 6900
      }
    ],
    "normalized_tcp_list": [
      1863,
      6901
    ],
    "normalized_tcp_ranges": [
      {
        "start": 6891,
        "end": 6900
      }
    ],
    "normalized_udp_list": [
      1863,
      6901
    ]
  }
]

Fixture coverage

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

Magic syntax

jc-rs ufw appjc-rs runs the command itself and parses what it prints. Recognised for: `ufw app`

Source: crates/jc-rs-parsers/src/security/ufw_appinfo.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