fraim@2.0.324
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or confirmed malicious behavior. The flagged telemetry and agent setup are tied to CLI setup flows, use a local metrics receiver, and write FRAIM-specific integration files.
Decision evidence
public snapshot- package.json declares the CLI entrypoints and no lifecycle script; the package starts through its CLI entrypoints.
- Claude telemetry settings enable OTLP metrics to a loopback endpoint and preserve existing user values.
- Telemetry setup is reached through CLI setup commands, including `add-ide` and `init-project`.
- The metrics receiver binds to 127.0.0.1, and snapshot retrieval also uses loopback.
- Agent integration writes FRAIM-specific files only in FRAIM-named locations or managed sections.
- Reviewed utilities show scoped setup, path checks, and git URL restrictions; no separate attack behavior was established.
Source & flagged code
18 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.324.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.324 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.