shipper auth status
shipper auth status
Section titled “shipper auth status”Usage: shipper auth status [options]
Show Shipper license status
Arguments
Section titled “Arguments”| Argument | Required | Description | Choices |
|---|---|---|---|
| None | - | - | - |
| Long | Short | Value | Default | Description | Choices |
|---|---|---|---|---|---|
| —json | - | - | false | output license status as JSON | - |
Examples
Section titled “Examples”Perform a live license inspection and show the canonical human status.
shipper auth statusPrint the allowlisted canonical license decision fields as JSON.
shipper auth status --jsonExit Codes
Section titled “Exit Codes”| Code | When |
|---|---|
| 0 | The canonical decision reports allowed: true. |
| 1 | The canonical decision reports allowed: false, or live inspection fails before returning a decision. |
Constraints
Section titled “Constraints”- The six canonical states are
signed-out,valid,offline-grace,expired,revoked, andterms-outdated;validis marked active in human output. - When present, human output shows the signed-in user, JSON-serialized entitlements, last-validated time, and grace-window end.
- Canonical gate guidance for non-healthy states is printed verbatim without command-authored recovery prose.
- Exit status follows the decision’s
allowedvalue and is never inferred from a state list. - JSON output contains exactly
state,allowed, and the defined subset ofemail,entitlements,validatedAt, andgracePeriodEndsAt; it omits guidance and presentation prose. - Status performs the canonical live inspection. A fresh cached validation avoids the network, while stale validation may refresh or clear the stored credential after a server result.
- A throttled core-owned offline warning may still appear on stderr when
--jsonis used; stdout remains machine-readable JSON. - The command works without Shipper settings, GitHub authentication, or a Git repository.