fraim@2.0.322
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no install-time execution or concrete attack behavior. The flagged telemetry and agent setup paths are reached through FRAIM commands and use a loopback metrics receiver and FRAIM-named integration files.
Decision evidence
public snapshot- package.json names the CLI entrypoints and ends without a lifecycle script; index.js dispatches to the packaged CLI.
- Claude token telemetry is enabled through FRAIM setup commands, which fill missing user settings with a localhost endpoint.
- The OTLP receiver binds to loopback and parses Claude token-usage metrics.
- Agent integration uses FRAIM-named skill and command files, with setup and sync performed through FRAIM flows.
- The flagged utility paths contain repository checks, doctor diagnostics, configuration handling, and marketplace validation; inspection found no attack behavior.
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.322.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.322 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.