The package has no npm install hook, but its explicit project setup installs persistent Claude hooks that collect project-local interaction data and influence later prompts. This warrants a warning for an agent capability, not a publish block, because the inspected behavior is project-scoped and no concrete exfiltration or other attack was established.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the project initialization command with Gofer enabled; the hooks then run during Claude prompt, tool, and stop events.
Impact
Project-local conversation-derived information can influence later agent prompts, and tool observations are retained in project files. Source inspection did not establish external transmission or credential theft.
Mechanism
The installer writes command hooks to the project’s Claude settings. Bundled scripts collect session and tool data into project-local bridge, observation, and memory files, and the prompt hook returns matching memories as additional context.
Evidence
dist/commands/init.jsdist/lib/gofer-installer.jsresources/gofer/hook-scripts/session-lifecycle.mjsresources/gofer/hook-scripts/user-prompt-submit.mjsresources/gofer/hook-scripts/post-tool-use.mjs