fraim@2.0.276
FRAIM core CLI and MCP package.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete unconsented install-time attack chain was found. The explicit CLI setup flow has broad agent-configuration and telemetry capabilities, so it warrants a warning rather than a block.
Decision evidence
public snapshot- First-run setup auto-configures every detected IDE, then installs user-level agent artifacts.
- Claude setup writes telemetry environment variables into ~/.claude/settings.json for all Claude Code sessions.
- The local MCP proxy sends usage events, including its API key, to the FRAIM remote API.
- package.json has no preinstall, install, or postinstall hook.
- The package bin only loads the CLI; setup changes require a user-invoked CLI/wizard flow.
- Telemetry receiver is configured for localhost:4318, not a direct external collector.
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.276.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.276 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.