custodian version

custodian version reports which build you are running. It prints three things: the version, the commit it was built from, and the SHA-256 checksum of the running program, computed by reading the program from disk at the moment you run it.

custodian version

custodian 1.4.0
commit 7c9e2a1b3f4d5e6a7b8c9d0e1f2a3b4c5d6e7f80
sha256 3b1f...c92a

The checksum reports what is actually running, not what the build intended, because it is computed from the bytes on disk. On a published release, it matches the checksum published for that download, so you can confirm the program has not been altered.

If the running program cannot be read to compute its checksum, the checksum line reads unavailable rather than failing.

Machine-readable output

--json emits the same three values as one object:

custodian version --json

{"version":"1.4.0","commit":"7c9e2a1b3f4d5e6a7b8c9d0e1f2a3b4c5d6e7f80","sha256":"3b1f...c92a"}

When the checksum is unavailable, sha256 is null.

Where the version and commit come from

The version and commit are stamped into the binary when it is built, not read from the environment when you run it. CUSTODIAN_VERSION and CUSTODIAN_COMMIT are compile-time build values, not runtime environment variables — setting them in your shell has no effect on what the command prints. A build that was not stamped with them — an ordinary local build from source — reports 0.0.0-dev for the version and unknown for the commit; a release build carries the real tag and the exact commit it was built from.