pulse-filetree

What the scan recorded

Observed events

every tool call, Read calls, Grep|Glob calls, classic hooks, every prompt

Hooks

session.start, command.run {command=filetree}, tool.call, tool.call {tool=Read}, tool.call {tool=Grep|Glob}, ui.message, classic.SessionStart, classic.CwdChanged, classic.FileChanged, ui.focus {component=Pane, requestId=filetree}, ui.scroll {component=Pane, requestId=filetree}, prompt.submit, prompt.attachment, ui.render {component=Pane, requestId=filetree}

API calls

$.clock.after, $.clock.every, $.clock.now, $.command.register, $.env.get, $.fs.list, $.fs.read, $.fs.stat, $.process.run, $.session.cwd, $.session.id, $.session.surfaces, $.state.get, $.state.set, $.ui.close, $.ui.copy, $.ui.invalidate, $.ui.open, $.ui.resolve, $.ui.toast

Surface modules

hooks/button.tsx, hooks/rows.tsx

Validation on 2.1.312

Passed

Scanned revision

5d1454ecadbe

Marketplace passed

pulse-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. pulse-filetree/hooks/register.tsx:242, pulse-filetree/hooks/register.tsx:352, pulse-filetree/hooks/register.tsx:654, pulse-filetree/hooks/register.tsx:849, pulse-filetree/hooks/register.tsx:944, pulse-filetree/hooks/tree.ts:169, pulse-filetree/hooks/tree.ts:208

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. What a mod can access and how the scan works.