fraim@2.0.283
FRAIM core CLI and MCP package.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found no lifecycle hooks, stealthy execution, credential harvesting, or remote payload chain. The package nevertheless performs user-level multi-agent integration and telemetry configuration during setup, so it warrants a warning for extension lifecycle risk.
Decision evidence
public snapshot- The user-driven first-run flow installs FRAIM artifacts into detected AI-agent configuration directories.
- The global installer updates FRAIM-owned files in Claude, Codex, Cursor, Grok, Gemini, Windsurf, and Kiro configuration areas.
- A telemetry helper can add OpenTelemetry environment settings to Claude Code's user settings.
- package.json declares no preinstall, install, or postinstall lifecycle hook.
- The inspected entrypoints only load the CLI when invoked directly.
- The telemetry endpoint is local, and no source evidence showed credential theft, remote payload execution, or covert exfiltration.
- The agent-config writes are named FRAIM artifacts and occur in explicit setup or first-run flows.
Source & flagged code
11 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.283.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.283 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.