fraim@2.0.338
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The telemetry configuration is part of explicit setup, targets a local receiver, and preserves existing settings.
Decision evidence
public snapshot- package.json identifies a CLI package and its entrypoints; the inspected manifest has no lifecycle hook.
- Claude telemetry settings target the local OTLP receiver, and the helper preserves existing environment values.
- IDE integration installs FRAIM-specific discovery files; project adapters name FRAIM-specific files.
- Diagnostics redact FRAIM keys; inspected first-run code handles command errors and agent-option lookup.
- Other cited locations are utility, setup, doctor, or sync modules; inspected excerpts do not establish malicious behavior.
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.338.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.338 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.