fraim@2.0.349
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged source resolves to FRAIM CLI, setup, diagnostics, metrics, and registry-learning behavior; package.json defines CLI entrypoints without lifecycle scripts. Claude metrics are enabled through setup commands and sent to a loopback receiver, while usage analytics go to the configured FRAIM service; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json exposes CLI entrypoints; inspection found no npm lifecycle hook or runtime dependency on fraim itself.
- Claude telemetry settings are added by project setup commands and configure metrics export to a local receiver.
- The receiver extracts token and cost metrics and binds to loopback; the token adapter reads its local snapshots.
- The MCP proxy uses the configured FRAIM service endpoint and API key; usage analytics select limited tool metadata and are sent to that endpoint.
- Agent setup writes FRAIM-specific skills and commands. The flagged diagnostics and runtime code handle redaction and setup state.
- The remaining flagged modules implement local learning, validation, provider, and user-invoked project operations; no separate attack chain was established.
- CLI setup enables Claude Code metrics in user-level settings without a separate telemetry consent prompt; the inspected receiver is loopback-bound and handles usage metrics.
- The proxy sends usage analytics and its API key to the configured FRAIM endpoint; the default is the package-aligned FRAIM service.
Source & flagged code
16 flagged · loading sourcePackage source references child process execution.
dist/registry/scripts/learning/run-publication.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.349.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.349 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.