fraim@2.0.301
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest exposes the FRAIM CLI, and inspected agent configuration behavior is associated with setup actions. The scanner’s similarity labels did not correspond to verified attack behavior in the reviewed source.
Decision evidence
public snapshot- The manifest identifies a CLI entrypoint, and the reviewed setup helpers are invoked by FRAIM CLI setup actions rather than package lifecycle hooks.
- The Claude settings helper configures metrics for a local receiver; the diagnostic helper masks known secrets and FRAIM keys in output.
- The inspected integration helpers install FRAIM-specific invocation files, while other flagged helpers inspect repositories, check configuration, or prepare installer output.
- Static similarity findings are review leads; the inspected excerpts do not establish malicious behavior.
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.301.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.301 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.