fraim@2.0.335
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe similarity alerts were not borne out by the inspected source. The global telemetry setting is activated through user-run setup commands, targets a loopback receiver, and no concrete attack behavior was identified.
Decision evidence
public snapshot- The manifest exposes CLI entrypoints and has no lifecycle hook or runtime self-dependency.
- Claude telemetry configuration is applied by the add-ide and init-project commands, writes settings only when keys are absent, and points to a loopback receiver.
- The OTLP receiver binds to 127.0.0.1; the inspected source does not establish an unrelated telemetry recipient.
- The integration helpers use FRAIM-specific agent files; inspected Git, diagnostic, and marketplace code performs product operations.
- Claude telemetry setup writes to the user-level settings file and can affect all Claude Code sessions across projects.
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.335.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.335 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.