opschain admin packs list

Included from Basic tier

Lists installed pack versions, newest install first within each pack: the entitlement each requires, its minimum platform version, pin state, what references it, file count and signing key. The CLI drains the server's pages for you.

opschain admin packs list
NAME                          VERSION  REQUIRES              MIN_PLATFORM  PINNED  REFERENCED BY    FILES  KEY
opschain-pack-infrastructure  1.2.3    packs:infrastructure  5.4.0         yes     0 tv / 0 runs    24     2026-a
opschain-pack-infrastructure  1.2.2    packs:infrastructure  -             no      2 tv / 3 runs    23     2026-a

REFERENCED BY is <n> tv / <m> runs: the template versions whose sealed set pins the version and the runs holding it — the two counts admin packs delete refuses over (re-resolve moves the template versions; retention releases the runs). -o, --output json|yaml emits the version rows, each carrying the bundle's content digest and size, referenced_by (the sealing template versions: project_code, template_code, template_id, template_version, template_version_id) and run_count.

Flags

Flag	Meaning
--name <pack>	List one pack's versions only.
--server <url>	Server base URL (default: the active context / OPSCHAIN_SERVER).
--auth-token <token>	Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login).
--filter <column>[!]=<value>	Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased; * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Applied client-side. Grammar: opschain docs cli.

See also

• opschain docs cli/admin-packs — the family overview.