git-atlas

What the scan recorded

Observed events

every tool call, Bash calls

Hooks

session.start, session.end, command.run {command=atlas}, turn.start, turn.complete, tool.call, tool.call {tool=Bash}, ui.render {component=AbovePrompt}, ui.render {component=Pane, requestId=git-atlas}

API calls

$.clock.after, $.clock.every, $.command.register, $.env.get, $.fs.stat, $.process.run, $.prompt.fill, $.session.cwd, $.session.id, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.keys, $.store.set, $.ui.ask, $.ui.log, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

e568eab4c92c

Marketplace passed

fluidz-mods

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. plugins/git-atlas/src/git/detail.ts:9, plugins/git-atlas/src/git/detail.ts:13, plugins/git-atlas/src/git/detail.ts:91, plugins/git-atlas/src/git/detail.ts:92, plugins/git-atlas/src/git/refs.ts:20, plugins/git-atlas/src/git/refs.ts:60, plugins/git-atlas/src/git/snapshot.ts:103, plugins/git-atlas/src/git/status.ts:8, plugins/git-atlas/src/guards/secret-add.ts:29

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.