Allowed by default with warning: agent-facing configuration or capability changes need review before use.
AI security review
scanned · by lpm-firewall-ai
Static inspection found project-level Claude hooks installed by the explicit scaffold command, enabled by default, that consume prompt and tool-event data and store related state locally. The source supports a guarded agent-capability warning, but does not establish install-time mutation, credential exfiltration, or an unsolicited account action.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs eai init or eai create with Gofer enabled, which is the default; later Claude hook events run within that project. Refreshing existing assets requires eai gofer refresh.
Impact
Claude sessions in the project receive Gofer-provided context, and project activity is persisted locally. No external credential recipient or network transfer was established for these hooks.
Mechanism
The CLI writes UserPromptSubmit, PostToolUse, and Stop commands into the project’s .claude/settings.json. The bundled scripts process prompt and tool-event data, add context to prompts, and write observations, memory, and session state under project-local .specify paths.
package.json ends after dependencies with no lifecycle script; the CLI registers init and create as commands.
The init command advertises Gofer assets installed by default with a --no-gofer opt-out, and calls the Gofer installer during scaffolding.
The installer copies bundled assets into the project and writes Claude event hooks to .claude/settings.json; refresh calls the same hook installer.
The installed hooks add context to prompts, save tool inputs and responses as project observations, and store learned memories locally. The session lifecycle hook updates a local bridge file.
The project-manifest target checks for an existing .claude directory during legacy scaffold detection. Gofer refresh is an explicit command, and --check previews changes before the user runs refresh to apply them.
The requested account-related source locations resolve to error reporting, redaction, validation, or explicit platform command flows; the inspected excerpts do not show an unsolicited account action.
Evidence against
No install-time trigger or external credential recipient was established for this setup path; the observed hook writes are project-local.
Refresh can be previewed with --check and otherwise requires the user to run the refresh command.