fraim@2.0.279
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no installation hook or confirmed attack behavior. The notable telemetry configuration is reached through explicit CLI setup and sends token metrics to a local receiver, so the scanner similarity flags do not support a malicious verdict.
Decision evidence
public snapshot- The manifest exposes CLI entry points and defines no installation lifecycle scripts.
- Claude Code token metrics are configured for a local receiver during explicit setup; the inspected code shows no remote telemetry destination.
- Agent integration writes FRAIM-named commands, skills, or managed project sections when setup functions run.
- The reviewed diagnostic and utility code handles local checks, configuration, repository operations, and FRAIM session cookies.
- The reviewed command and service entry points show product setup and user-invoked operations, with no confirmed attack 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.279.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.279 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.