fraim@2.0.326
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior; the scanner similarity labels and incomplete static analysis are not proof of malicious activity. The observed telemetry and agent configuration are activated through user-invoked setup flows and target FRAIM or a local receiver.
Decision evidence
public snapshot- package.json exposes the CLI entrypoints; index.js loads the compiled CLI. The inspected manifest has no lifecycle scripts.
- Claude token metrics are configured to use a loopback endpoint when the user invokes add-ide or init-project; the setup writes user settings.
- Agent integration installs FRAIM-specific files, and first-run/user-level setup calls the corresponding integration functions.
- Doctor diagnostics redact known tokens; connectivity checks probe the configured FRAIM server or run a configured stdio MCP server.
- Repository utilities constrain local paths and accepted Git URL forms; the override command rejects traversal and absolute paths.
- The inspected installer, marketplace, and cookie code supports product installation, secret detection, and FRAIM session cookies.
Source & flagged code
18 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.326.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.326 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.