fraim@2.0.321
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected source shows user-invoked setup behavior, FRAIM-specific agent integration files and local-proxy telemetry. The scanner similarity labels and static-analysis limitations do not establish malicious behavior.
Decision evidence
public snapshot- The manifest declares CLI entrypoints and no lifecycle scripts.
- Claude telemetry settings are added by IDE setup paths and point to the local proxy; existing settings are preserved.
- Agent adapters use FRAIM-specific project paths, and the doctor diagnostic code sanitizes known secrets.
- The remaining inspected paths cover local overrides, setup, repository handling, installer generation, cookies and connectivity; no attack behavior was identified.
- IDE setup enables Claude token telemetry for later sessions, including sessions outside the project where setup ran.
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.321.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.321 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.