fraim@2.0.273
FRAIM core CLI and MCP package.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection confirms guarded, user-command-driven AI-agent and shell configuration mutation, but no unconsented npm lifecycle execution or covert exfiltration. Warn rather than block under the stated install-control policy.
Decision evidence
public snapshot- The user-invoked first-run flow persists PATH, auto-configures detected IDE MCP files, and installs global rules.
- `init-project` enables telemetry in Claude Code’s user-wide settings when Claude Code is detected.
- Generated MCP configuration registers third-party `npx` servers and a FRAIM server carrying an API key and remote URL.
- package.json defines no preinstall, install, postinstall, or other lifecycle scripts.
- Observed mutations are reached through explicit CLI setup/first-run/init-project actions, not package installation.
- No source-confirmed credential harvesting or covert exfiltration was found; remote access is tied to FRAIM MCP use.
Source & flagged code
11 flagged · loading sourcePackage source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9Package source references dynamic require/import behavior.
bin/fraim.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to fraim@2.0.273.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.273 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.