shipper-cli

CLI adapter for Shipper.

Most users should install shipper, not this crate:

cargo install shipper --locked

This becomes the supported crates.io path after the v0.4.0 publish completes.

For reproducible 0.4.0 installs, pin the version:

cargo install shipper --version 0.4.0 --locked

Use this crate when

You need the exact clap-based CLI surface programmatically — for example, a wrapper that invokes Shipper after extra preflight steps of your own:

fn main() -> anyhow::Result<()> {
    // ... custom preflight ...
    shipper_cli::run()
}

Or you want to install the adapter binary directly:

cargo install shipper-cli --version 0.4.0 --locked

That adapter binary runs the same code path as the shipper facade.

For programmatic use without the clap graph, depend on shipper-core instead — that's the lean embedding surface.

Architecture

shipper (install face — `cargo install shipper`)
  -> shipper-cli (this crate — CLI adapter, pub fn run())
       -> shipper-core (engine, no CLI deps)

Related

• Install face: https://crates.io/crates/shipper
• Engine library: https://crates.io/crates/shipper-core
• Project README: https://github.com/EffortlessMetrics/shipper#readme

License

MIT OR Apache-2.0.