Skip to main content
The current public CLI is intentionally narrow. Supported commands:
Unsupported commands are not part of the public OSS surface, including show, import, registry, list, tag, baseline, unpack, and config.

​
Choose the right command

​
Global help

For a clean-shell trial, use:
Command-specific help is also available:

​
Command behavior summary

​
Output style

The CLI uses line-oriented plain text output rather than JSON. That makes it easy to read in a terminal and easy to consume from shell scripts. Examples:
  • pack prints input=, output=, name=, digest=, files=, bytes=
  • inspect prints path=, name=, version=, digest=, files=, bytes=
  • verify prints ok=true or ok=false
  • compare prints ok=, summary counts, and per-file change lines
Most users start here:
  1. pack the output directory.
  2. inspect the resulting artifact.
  3. verify it before trusting or sharing it.
  4. compare it against a baseline when you care about repeated-run drift.
Use CLI workflows for end-to-end patterns.

​
Core library mapping

The CLI is a conservative wrapper around @filepacks/core:
  • CLI pack -> pack()
  • CLI inspect -> inspect()
  • CLI verify -> verify()
  • CLI compare -> compare()
Use the core package when you need structured results in code.