fraim@2.0.280
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no install hook, runtime self-dependency, or concrete malicious behavior. The flagged global telemetry change is reachable through explicit setup commands and sends metrics to a loopback receiver.
Decision evidence
public snapshot- package.json identifies the CLI and has no lifecycle script; its dependency list does not include fraim.
- Claude token telemetry is enabled only through the add-ide and init-project setup paths; it writes metrics settings to ~/.claude/settings.json and uses a localhost endpoint.
- The IDE integration paths install FRAIM-named skills and commands, and the metrics receiver listens on loopback.
- The inspected diagnostics and other flagged utilities show secret sanitization, repository validation, setup, syncing, and product service behavior.
Source & flagged code
19 flagged · loading sourcePackage source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9Package source references shell execution.
dist/src/cli/doctor/checks/scripts-checks.jsView on unpkg · L170Findings
Affected versions and remediation
This report applies to fraim@2.0.280.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.280 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.