shipmoor: command not found
The installer puts the binary at ~/.shipmoor/bin/shipmoor and prints the PATH update if needed:
export PATH="$HOME/.shipmoor/bin:$PATH"
shipmoor version
# shipmoor 0.10.0A product command asks me to authorize
Every installation requires account and device authorization. Complete the device flow in the browser; the interactive CLI then resumes the original command. Check the resulting state with:
shipmoor auth statusNew personal accounts receive 30 days of full Pro access without a card. If the flow cannot refresh, run shipmoor login directly and approve the device again.
A Free command says its allowance is exhausted
Free has four independent counters of five per month: Claim Check, Review, Test Evidence, and Blast Radius. Check all counters and the UTC renewal time with:
shipmoor usageUnused invocations do not roll over. Scan, Harness, and Skills remain unlimited. Upgrade to Pro for unlimited access to the four metered command families.
A Free metered command reports service unavailable
Free metered commands require the allowance service online for every invocation. They do not execute when consumption cannot be confirmed. Unlimited surfaces can continue while their signed lease and grace period remain valid.
CI reports authentication required
Current self-managed CI supports Scan only. Create a scan-scoped machine token and store it as the SHIPMOOR_TOKEN CI secret. Expose it through the process environment, not a file or command-line argument.
Do not use interactive refresh credentials in CI. The token does not authorize Claim Check, Review, Test Evidence, or Blast Radius.
A full-repository Scan reports many phantom imports
Scope the Scan to --changed, --staged, or --diff <range>, and make sure project manifests are present. See Scanning your code.
CI treats a finding as a tooling failure
Scan exit code 1 means the configured gate found a blocking result and still produced a complete JSON or SARIF report. Exit codes 2 and 3 represent usage/configuration and Scan failures. See Output formats & exit codes.
Still stuck?
Capture shipmoor version, the exact command, and stderr. Do not share device refresh credentials or SHIPMOOR_TOKEN. Scan reports can include findings and paths even though they do not include source content, so review them before sharing.