The source shows a first-party Gofer setup flow that can configure project-local agent hooks, so a warning is appropriate. The package manifest’s prepare script only runs the compiler, and the inspected hook behavior does not establish malicious activity.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI init flow with Gofer enabled; Gofer is skipped when disabled.
Impact
The configured hooks can run during later Claude Code activity and alter project-local state.
Mechanism
The installer writes command hooks into the project’s .claude/settings.json and installs Gofer resources. The session lifecycle script records session state in a local bridge file.
Evidence
dist/commands/init.jsdist/lib/gofer-installer.jsresources/gofer/hook-scripts/session-lifecycle.mjs