code-brain
Turn any codebase into searchable knowledge for Claude Code. LLM Wiki + AST Index + MCP Server.
This report shows the evidence for code-brain@0.9.0, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms concrete install-time writes into Claude Code control files, including persistent hooks that affect later agent behavior. Under the provided policy, unconsented npm postinstall mutation of a foreign/broad AI-agent control surface is blocking even without exfiltration. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json runs postinstall: node scripts/postinstall.cjs || true
- scripts/postinstall.cjs writes .claude/skills/code-brain/SKILL.md during install
- scripts/postinstall.cjs creates/appends CLAUDE.md with code-brain instructions
- scripts/postinstall.cjs mutates .claude/settings.json hooks to run npx code-brain session-start and pre-tool-nudge
- dist/hooks/adoption-hooks.js injects SessionStart and PreToolUse context steering Claude tool choice
- README.md openly documents the auto-wired Claude hooks
- Hook commands are package-aligned and call local code-brain CLI behavior
- No credential harvesting or exfiltration endpoints found in inspected files
- Dynamic require in dist/db/better-sqlite-driver.js only loads optional better-sqlite3
- Shell use is limited to user-invoked CLI features such as graph opener and git helpers
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
dist/db/better-sqlite-driver.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to code-brain@0.9.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing code-brain@0.9.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.