chage

--chagev1.1.0

Converts `chage --list` command output to JSON

Linuxcommand

$ chage --list | jc-rs --chage

A real pair

From the reference corpus (centos-7.7/chage.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.

chage --listcentos-7.7

Last password change					: never
Password expires					: never
Password inactive					: never
Account expires						: never
Minimum number of days between password change		: 0
Maximum number of days between password change		: 99999
Number of days of warning before password expires	: 7

expected outputjson

{
  "password_last_changed": "never",
  "password_expires": "never",
  "password_inactive": "never",
  "account_expires": "never",
  "min_days_between_password_change": 0,
  "max_days_between_password_change": 99999,
  "warning_days_before_password_expires": 7
}

Fixture coverage

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

Magic syntax

jc-rs chage --listjc-rs runs the command itself and parses what it prints. Recognised for: `chage --list`, `chage -l`

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