enumeray compatibility inspect

Report this executable’s compiled source/build identity and its installed-file SHA-256.

Use when: Record the actual binary before installation, compare a host with its package metadata, or save a timestamped peer observation.

Role and prerequisites: Any OS account allowed to run and read the selected executable. Only the executable is required. No configured profile, login, credentials or running API is required; inspect reads no login profiles, contacts no service and changes no journal or execution state.

Example

enumeray --json compatibility inspect

Compiled provenance identifies the running build. executable_sha256 hashes its current installed file and must not be substituted for an already-running connector’s reported build after binary replacement. A modified development content digest does not establish signed-release trust. Output is JSON; --json selects the compact machine-readable form.

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

Result and next step

Prints source repository/revision/tree/lockfile/content identity, source cleanliness, package/version/target, protocol versions, observed_at and executable_sha256. Exit 0 means the local observation succeeded; it is not release qualification or a compatibility verdict.

Retain the observation and compare it with independently selected release or development evidence using compatibility check. Use the extracted binary’s absolute path for a pre-install observation.

Exact syntax, defaults and accepted values

Report this executable's embedded provenance without loading login profiles

Usage: enumeray compatibility inspect [OPTIONS]

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