fraim@2.0.290
FRAIM core CLI and MCP package.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install lifecycle hook or automatic installation path was found, so the source does not meet the threshold for malicious install-hook abuse. The explicit user-command flow still makes broad agent configuration changes and collects telemetry, which warrants a warning.
Decision evidence
public snapshot- The explicit add-ide command installs global agent rules and skills after configuring an IDE.
- Claude Code setup writes user-level telemetry settings that route metrics to a local receiver.
- The MCP server reads the newest Codex session log to collect token totals.
- Collected usage events and the FRAIM API key are posted to the vendor analytics endpoint.
- A user-level launcher resolves and executes the latest fraim release through npx, creating update-chain risk.
- package.json has no preinstall, install, postinstall, or other lifecycle script.
- The reviewed configuration and telemetry actions require an explicit FRAIM CLI command or MCP-server start.
- The Codex adapter extracts token counters and model data rather than forwarding prompt contents.
Source & flagged code
16 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.290.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.290 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.