fraim@2.0.312
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install hook, and the telemetry setting is written from explicit CLI setup while preserving existing values and targeting a loopback receiver. The remaining flagged source inspected supports scoped setup, sync, diagnostics, and normal service behavior; source review found no concrete attack.
Decision evidence
public snapshot- The inspected manifest exposes a CLI entry point and has no install lifecycle script.
- Claude Code telemetry settings are added only during setup for a detected or selected Claude Code installation, and existing environment values are preserved. The configured metrics endpoint is a loopback receiver.
- IDE integration writes FRAIM invocation artifacts; project adapter writes are kept inside the project root. First-run and global sync invoke these setup helpers.
- Diagnostics sanitize known secrets, MCP checks use the configured remote URL and API key, and the other inspected flagged files handle CLI dispatch, scoped sync, validation, installer support, or cookies.
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.312.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.312 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.