fraim@2.0.298
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected source supports ordinary CLI, setup, and local MCP proxy behavior, with no lifecycle hook or concrete attack chain. Static similarity findings alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json declares CLI entrypoints and dependencies, with no lifecycle scripts or runtime dependency on fraim.
- Claude telemetry and IDE integration are set up through CLI commands; telemetry points to a local endpoint and managed files are limited to FRAIM artifacts.
- Project agent adapter writes require a validated FRAIM workspace root.
- Inspected diagnostic, Git, scripts, session, cookie, installer, marketplace, and MCP server code showed no confirmed attack behavior.
- The flagged entrypoint and helper files implement CLI startup, repository operations, local workflow loading, or marketplace validation.
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.298.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.298 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.