fraim@2.0.327
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe suspicious setup behavior is reachable through explicit CLI setup flows and configures Claude telemetry to use a local endpoint while preserving existing environment values. The manifest has no install hook, and the inspected diagnostics and agent integration behavior did not establish a concrete attack.
Decision evidence
public snapshot- package.json declares the CLI entry points and ends after dependencies, with no install lifecycle hook.
- Claude telemetry configuration sets an OpenTelemetry endpoint at localhost and preserves existing settings; the helper is called from CLI setup flows.
- Agent integration files use FRAIM-specific paths, while onboarding and user-level sync call the integration setup.
- The diagnostic helper redacts known secrets and FRAIM tokens; the remaining inspected paths support local diagnostics and repository or package setup.
- The initialization and IDE setup commands enable Claude token telemetry in user-level settings when Claude Code is detected.
Source & flagged code
17 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.327.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.327 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.