fraim@2.0.296
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found user-level telemetry configuration and FRAIM-owned agent setup reached through CLI flows, with metrics handled by a local receiver. The broader telemetry scope is a privacy consideration, but no concrete attack behavior was established.
Decision evidence
public snapshot- package.json identifies FRAIM’s CLI entrypoints; the reviewed behavior is provided by package source files.
- Claude Code token telemetry writes user-level settings and starts a local metrics receiver; the setup is called from CLI commands.
- IDE integration installs FRAIM-specific invocation files, while project adapters restrict writes to the project root.
- The inspected diagnostics, repository, workflow, installer, cookie, and marketplace code showed no confirmed attack behavior.
- The telemetry setup enables token metrics across Claude Code sessions, so its scope is broader than a single project.
Source & flagged code
17 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.296.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.296 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.