airlock

What the scan recorded

Observed events

the system prompt, Read calls, Edit calls, Write calls, NotebookEdit calls, Bash calls, Agent calls, EnterWorktree calls, ExitWorktree calls

Hooks

session.start, turn.start, turn.complete, ui.render {component=Pane, requestId=?}, prompt.section, tool.call {tool=Read}, tool.call {tool=Edit}, tool.call {tool=Write}, tool.call {tool=NotebookEdit}, tool.call {tool=Bash}, tool.call {tool=Agent}, tool.call {tool=EnterWorktree}, tool.call {tool=ExitWorktree}, command.run {command=airlock-status}, command.run {command=airlock-diff}, command.run {command=airlock-accept}, command.run {command=airlock-reject}, command.run {command=airlock-abort}, command.run {command=airlock-cleanup}, command.run {command=airlock-history}, command.run {command=airlock-mode}, command.run {command=airlock-begin}, command.run {command=airlock-rejected}, command.run {command=airlock-review}

API calls

$.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.stat, $.process.run, $.session.cwd, $.session.id, $.store.delete, $.store.get, $.store.keys, $.store.set, $.ui.ask, $.ui.close, $.ui.invalidate, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

0c7e681c9253

Marketplace passed

airlock-marketplace

UI rewrite review

UI hook source contains control-character strings. Review any values passed to next() as rewritten props.text; the scanner does not trace whether these strings reach that call. hooks/tx/commands.tsx:41, hooks/tx/commands.tsx:123, hooks/tx/patch.ts:31, hooks/tx/patch.ts:71

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.