fraim@2.0.302
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete malicious behavior. The scanner similarity alerts are not proof of an attack, and the telemetry behavior reviewed sends token metrics to a local receiver.
Decision evidence
public snapshot- The manifest identifies a CLI entrypoint and contains no lifecycle script declaration.
- CLI setup writes Claude Code telemetry settings that target a localhost receiver; the receiver accepts metrics locally.
- Agent integration files create FRAIM-specific skills, commands, and rules in named directories.
- The inspected diagnostics sanitize secret strings, while the cited repository and workflow helpers use product-specific operations.
- The other required finding paths contain CLI dispatch, local setup, repository detection, installer, marketplace validation, or cookie handling behavior; no concrete attack was identified.
- Static similarity alerts and global Claude telemetry configuration merit inspection, but the reviewed source does not show a harmful payload or external telemetry recipient.
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.302.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.302 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.