registry / agentic-cortex / 4.6.0

agentic-cortex@4.6.0

Persistent typed memory for AI coding agents — install & forget: auto-inject context via git hooks, 13 memory types, confidence tracking, conflict detection, grounded QA, codebase graphs

AI Security Review

scanned 14d ago · by lpm-firewall-ai

LPM flags this version as an AI-agent control-surface risk. Installing the dependency automatically modifies the parent project’s AI-agent instruction surfaces and Git hooks. These changes cause future agent sessions and Git events to invoke package-directed memory injection without an explicit setup command.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

npm install of agentic-cortex into another project

Impact

Unconsented persistent influence over Claude Code, Cursor, OpenCode, and Git-triggered project behavior.

Mechanism

postinstall writes foreign AI-agent rules, Git hooks, and injected project context

Policy narrative

On dependency installation, the postinstall script targets npm’s parent project directory. It creates AI-agent discovery/instruction files for Claude Code, Cursor (with alwaysApply), and OpenCode, injects generated content into knowledge.md, and adds Git hooks that rerun injection after repository actions. This is an unconsented install-time mutation of foreign AI-agent control surfaces and establishes persistence in the consuming project.

Rationale

Direct source inspection confirms a postinstall chain that writes broad third-party agent control files and persistent Git hooks in the parent project. This meets the firewall block boundary regardless of the package’s stated memory feature.

Evidence

package.jsonscripts/auto-setup.jsscripts/create-discovery-files.jsscripts/inject-memory.mjssrc/core/session.jssrc/core/constants.jsknowledge.md.claude/CLAUDE.md

agentic-cortex@4.6.0

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code