worktrees-manager-mod

What the scan recorded

Observed events

every prompt, Bash|PowerShell calls, EnterWorktree|ExitWorktree calls, classic hooks

Hooks

session.start, command.run {command=worktrees}, ui.close, prompt.compose, prompt.submit, tool.call {tool=Bash|PowerShell}, tool.call {tool=EnterWorktree|ExitWorktree}, command.run {command=cd}, classic.CwdChanged, turn.complete, turn.start, turn.step, classic.Stop, session.end, classic.SessionStart {source=clear|resume|fork}, ui.render {component=Pane}

API calls

$.clock.every, $.clock.now, $.command.list, $.command.register, $.command.run, $.env.set, $.fs.exists, $.fs.read, $.fs.write, $.model.complete, $.process.run, $.session.cwd, $.session.id, $.session.model, $.settings.read, $.store.delete, $.store.get, $.store.keys, $.store.set, $.tool.call, $.ui.copy, $.ui.invalidate, $.ui.log, $.ui.open, $.ui.resolve, $.ui.status, $.ui.toast

Validation on 2.1.302

Passed

Scanned revision

fd415a0aaf42

Marketplace passed

claude-worktrees-mod

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/register.js:112, hooks/register.js:139, hooks/register.js:157, hooks/register.js:801

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.