@memxai/cairn@0.3.3
Cairn — an append-only journal for AI agents. Git-like memory, without the complexity.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe install hook unconsentedly mutates global and project AI-agent control surfaces. The opt-outs do not provide affirmative consent, so this meets the blocking policy for install-time agent control changes.
Decision evidence
public snapshot- package.json runs scripts/postinstall.mjs during installation.
- The postinstall script invokes global setup for global installs and project setup for local installs; neither requires affirmative consent.
- Global setup writes Cairn rules into global agent instruction files, including Claude Code’s primary file.
- Project setup installs a Claude Code SessionStart hook in the consumer project’s .claude/settings.json.
- The package provides environment-variable opt-outs, but they default off and do not require affirmative consent before these changes.
Source & flagged code
6 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 child process execution.
dist/setup/install.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @memxai/cairn@0.3.3.
See all versions of @memxai/cairn for other recorded verdicts.
- Avoid installing @memxai/cairn@0.3.3. 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.