Verdict — DeadBolt
The permanent record behind this listing's marks. Cite the JSON form; the hash lets anyone confirm the verdict they were quoted is the one published here.
- Verification state: evidence
- Last reviewed: 2026-11-14
- Listing: DeadBolt · Machine-readable verdict: /verdicts/deadbolt.json
- Content hash (SHA-256):
000a3cd430976de0a0bb0aa4d13dc75b4dd534f2f77ff943eb97716008baf8aa
Criteria
- Approval gates: Built in — Operator approval for configured irreversible tools; exact-action grants through a trusted adapter.
- Restart recovery: Not claimed — DeadBolt keeps its lease and policy state in a private store, but it does not resume agent work. Pair it with a durable workspace or engine.
- Evidence trail: Built in — The operator store keeps run, decision and approval records.
- Kill switch: Built in — Kill withdraws a run's lease so further gated actions are refused.
- Policy controls: Built in — Tool policy, destination policy, ancestor policy and fixed run deadlines.
- Sandbox isolation: Not claimed — DeadBolt is a gate, not a sandbox. Keep OS access, child-process credentials and network isolation explicit.
Evidence
- Evaluation notes, October 2026
- CI runs
- v2.0.2 release with checksums
- Python client on PyPI (n11-deadbolt-client)
- Homebrew cask (n11-deadbolt)
The hash covers the verdict body published at the JSON URL: slug, name, vendor, owner, page, verification state, review date, criteria marks and evidence links. If any of those change, the hash changes and the review date moves.