──[ ▮ ]── changelog
Changelog
Every release, every rule. npm i -g @agenticcli/shipguard@latest
+ added~ fixed! breaking
v0.5.1jul 20, 2026
Release-signing hardening
- Release attestation now signs with real production keys, checked for freshness in CI on every publish
- Fixed an npm
bin path warning and added a publish-guard sentinel so a broken package can't reach latest
v0.5.0jul 19, 2026
Verdict-neutral exit codes + fail-loud Pro scans
- Exit codes are verdict-neutral:
0 means the scan completed (read the JSON recommendation field), not "safe" — 1 only blocks with --strict - A failed Pro-tier fetch now fails loud with exit
3 instead of silently degrading to a free scan — opt in to the old behavior with --allow-degraded scanId now persists across process restarts, closing a retry gap that could double-charge a Pro scan- Local observability store for scan history and regression checks
v0.4.1jul 6, 2026launch
ShipGuard is live
- Five local check modules:
secrets, auth, payments, database, deployment — free and unlimited, no account - Deterministic exit codes:
0 scan completed (verdict in the JSON recommendation field) · 1 blocked (with --strict) · 2 config error · 3 runtime error --json and --changed output for CI and agent workflows- Cloud scans against the full rule corpus, memory-only, never written to disk — Free, Plus, and Pro tiers
shipguard init scaffolds a policy file and a CI gate in one command