Source inspection found a real project-level agent integration: Gofer setup and refresh install Claude hooks in project settings. Because activation is through CLI setup or update operations rather than an npm install hook, this is a warning for guarded agent extension setup, not a confirmed malicious attack.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs Gofer setup during project initialization or applies a project update that refreshes Gofer assets.
Impact
Claude may run package-provided project hooks during its configured events. This is a guarded, first-party extension setup capability and warrants a warning under the agent integration policy.
Mechanism
The CLI writes hook commands into the project’s .claude/settings.json; refresh invokes the same hook installer. The lifecycle script accesses a project-local bridge file.
Evidence
dist/lib/gofer-installer.jsdist/lib/gofer-refresh.jsresources/gofer/hook-scripts/session-lifecycle.mjs