The package’s update and Gofer behavior is command-triggered, but its default project refresh overwrites existing Claude hook arrays without preserving their entries. That can disable other project integrations, so this merits a warning for agent configuration risk.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `eai update` with project refresh enabled, or explicitly initializes a project with Gofer assets.
Impact
Existing project hooks in those slots may be removed, changing other agent integrations. This is a configuration integrity risk, not evidence of a concealed attack.
Mechanism
Gofer refresh assigns its own commands to three hook arrays and writes the settings object back, without merging existing entries in those arrays.
Evidence
dist/commands/update.jsdist/lib/gofer-refresh.jsdist/lib/gofer-installer.js.claude/settings.json.specify/scripts/hooks/user-prompt-submit.mjs.specify/scripts/hooks/post-tool-use.mjs.specify/scripts/hooks/agent-stop.mjs