fraim@2.0.289
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected setup behavior is reached through CLI configuration flows. Telemetry targets a loopback receiver, while agent integrations create FRAIM-specific files; no concrete attack behavior was found.
Decision evidence
public snapshot- The inspected manifest defines CLI entrypoints and has no lifecycle scripts.
- Telemetry settings are added by IDE or project setup and direct Claude token metrics to a local receiver bound to loopback.
- Agent setup writes FRAIM-specific files and gives guidance to use FRAIM only when explicitly requested.
- The highlighted utilities support scoped Git, project sync, diagnostics, and secret scanning; no credential transfer to an unrelated recipient was identified.
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.289.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.289 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.