Shipwrit
From its catalog listing
Outcome-based release verification for Hermes: detect false-green deployments with bounded user journeys and redacted evidence receipts.
Good to know before installing
sends the HTTP requests in the project's release-witness.json (GET by default; POST/PUT/PATCH/DELETE steps when writes are allowed) to the hosts that file lists, which may include localhost or LAN addresses; writes receipts and release state under `.release-witness/` in the working directory, and its pre_verify hook can ask the agent to keep working when a detected deploy command has no passing receipt.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install shipwrit - Said no? Turn it on later:
hermes plugins enable shipwrit - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Security & privacy · Automation & multi-agent
- Maintained by
- ShalyX (Community)
- Needs
- No API keys declared
- Adds tools
release_witness_check- Adds hooks
post_tool_callpre_verify- Works on
- linux, macos, windows
- Version
- 0.3.2
- In the catalog
- 2026-11-10
Known issues (from its catalog listing)
- HTTP/JSON contracts only; browser-based and visual journeys are not supported.
- The pre_verify continuation is advisory, only runs in coding turns after file edits, and does not block deployment infrastructure.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher