fraim@2.0.340
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no lifecycle hook, and its entrypoints run the CLI when invoked. Claude telemetry setup is tied to CLI setup flows and sends token metrics to a loopback receiver; the inspected source does not establish a concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI and defines no lifecycle hook; the launchers load the CLI when invoked.
- Agent setup writes FRAIM invocation files through setup flows. The inspected telemetry path configures a loopback metrics receiver and handles token metrics.
- The inspected diagnostics, Git, and sync utilities have scoped product behavior, including secret redaction, an allowlisted Git transport, and MCP connectivity checks.
- The override command validates relative paths before creating an override.
- When Claude Code is detected, setup adds telemetry environment variables to the user-level Claude settings file.
Source & flagged code
16 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 · L235Findings
Affected versions and remediation
This report applies to fraim@2.0.340.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.340 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.