enumeray compatibility

Inspect the executable and compare an explicitly selected installation without changing service or execution state.

Use when: Acquire a matching client, check a connector or runner observation, or retain evidence before a deliberate software change.

Role and prerequisites: Any holder of an installed executable; connector diagnostics additionally require current connector inspection authority. Install the intended executable. Inspect and local/saved-snapshot checks need no configured profile, login or running API. A live check needs the selected API origin; only connector diagnostics need a static bearer token.

Example

enumeray --json compatibility inspect

Every command also accepts the profile, API, JSON and timeout options.

Choose a subcommand

Command	Purpose
inspect	Report this executable’s compiled source/build identity and its installed-file SHA-256.
check	Compare the selected software/evidence and write a new private installation receipt without repairs, credential renewal or execution.

Result and next step

Choose inspect for local compiled provenance or check for a saved comparison receipt. The command group itself performs no operation.

Use the canonical installation and maintenance guide to acquire the selected evidence before comparing it.

Exact syntax, defaults and accepted values

Inspect installed build identity and compare an explicitly selected component set

Usage: enumeray compatibility [OPTIONS] <COMMAND>

Commands:
  inspect  Report this executable's embedded provenance without loading login profiles
  check    Compare selected identities without repairs, credential renewal or execution
  help     Print this message or the help of the given subcommand(s)

Options:
      --api <API>          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --profile <PROFILE>  Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>    Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json               Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>  User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help               Print help