noqtis-inspect(1)
NAME
noqtis-inspect —
show what a capsule says, without checking it
SYNOPSIS
noqtis inspect |
[-j | --json]
dir |
DESCRIPTION
noqtis inspect reads the seal
noqtis.sig and the manifest
noqtis.json of the capsule dir
(noqtis-capsule(5))
with the same strict readers as
noqtis-check(1)
and prints what they say:
- format
- the manifest's format,
‘
noqtis-capsule-1’ - alg
- the seal's signature algorithm
- key
- the SHA-256 of the seal's public key, in hex: the key's fingerprint
- created
- the manifest's creation time (RFC 3339, UTC)
- files
- the number of files the manifest lists
- bytes
- their total size
- timestamp
- ‘
present’ when the seal carries an RFC 3161 timestamp, ‘none’ otherwise - meta
- the manifest's ‘
meta’ object (canonical JSON), when it has one
Nothing is checked: not the manifest's digest, the signature, the timestamp or any file. The last line says so; run noqtis-check(1) to check the capsule. When the seal or the manifest does not parse, the failing rows are printed as by noqtis-check(1).
-j,--json- Print one line of JSON instead:
{"capsule":"<dir>","checked":false,"format":"<format>","alg":"<alg>", "key_sha256":"<hex>","created":"<time>","files":<n>,"bytes":<n>, "timestamp":<bool>,"meta":<object or null>}or, when the capsule cannot be read,
{"capsule":"<dir>","checked":false, "errors":[{"check":"<name>","detail":"<text>"},...]}
EXIT STATUS
- 0
- the seal and the manifest parse (nothing is checked)
- 1
- one of them does not parse
- 2
- a usage error, or the path is not a folder
EXAMPLES
$ noqtis inspect results
format noqtis-capsule-1
alg ML-DSA-65
key da278e20d47d35382abfa1c10352e1800c33fb5b1a2b725fc24ef18200b41ef7
created 2026-10-29T14:59:18Z
files 2
bytes 6
timestamp none
meta {"project":"demo"}
results: read, not checked (run `noqtis check` to check it)
SEE ALSO
noqtis(1), noqtis-check(1), noqtis-seal(1), nqinsp(3), noqtis-capsule(5)