One universal Shipmoor 0.10.0 binary serves Free and Pro. Every installation must be authorized to an account before product commands execute.
Product commands
| Command family | Free | Pro | Guide |
|---|---|---|---|
shipmoor scan | Unlimited | Unlimited | Scanning your code |
shipmoor claim-check | 5 invocations/month | Unlimited | Claim Check CLI |
shipmoor review | 5 invocations/month | Unlimited | Code Review CLI |
shipmoor test-evidence | 5 invocations/month | Unlimited | Test Evidence CLI |
shipmoor blast | 5 invocations/month | Unlimited | Blast Radius CLI |
shipmoor harness | Unlimited | Unlimited | Agent Harness |
shipmoor skills | Unlimited | Unlimited | Agent Skills |
shipmoor rules and shipmoor explain are part of the unlimited Scan workflow. Use each command’s dedicated reference for its verified flags and subcommands; there is no shipmoor verify umbrella command.
Authorization and usage
| Command | Purpose |
|---|---|
shipmoor login | Start device authorization directly |
shipmoor logout | Remove the local device session |
shipmoor auth status | Show account, device, and effective plan |
shipmoor usage | Show all four command allowances and renewal time |
shipmoor auth token create --name <name> --scope scan | Create a Scan-only machine token for self-managed CI |
An unauthorized interactive product command starts device authorization and resumes after approval. Non-interactive environments fail with SHIPMOOR_TOKEN guidance rather than waiting for a browser.
Help, version, login, logout, and doctor are available before authorization. Setup-only and non-execution subcommands documented by each command do not consume a Free allowance.
Allowance admission
A valid Free metered invocation consumes one unit after argument and configuration validation but before engine, model, runner, evidence collection, or output work. Once admitted, it counts even if the result is blocked, inconclusive, canceled, or failed. A rerun consumes another unit.
User and agent invocations share the same counters. Internal Review or Test Evidence work composed beneath one admitted Claim Check does not consume another bucket. Authentication and allowance messages go to stderr for machine-output commands.
Environment variables
| Variable | Purpose |
|---|---|
SHIPMOOR_TOKEN | Scan-scoped self-managed CI authorization; environment only |
SHIPMOOR_VERSION | Pin the universal installer, for example 0.10.0 |
SHIPMOOR_CHANNEL | Select a published install channel |
SHIPMOOR_INSTALL_DIR | Set a custom install location |
NO_COLOR | Suppress color output |
Current self-managed CI supports Scan only. SHIPMOOR_TOKEN does not authorize Claim Check, Review, Test Evidence, or Blast Radius in CI.