fraim@2.0.284
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe high similarity scanner labels did not establish malicious behavior in the inspected source. The agent configuration and telemetry changes are tied to explicit CLI setup, and the examined code did not show a concrete attack surface.
Decision evidence
public snapshot- package.json identifies the package entrypoints and dependencies; inspection found no lifecycle hook or runtime self-dependency.
- Claude token telemetry is configured by the explicit `add-ide` and `init-project` commands. It sends metrics to a local receiver, and the inspected receiver and proxy are part of FRAIM’s MCP setup.
- Agent setup code targets FRAIM-specific skill and command files; the global integration checks for an existing Claude directory before writing.
- The diagnostics code redacts known secrets and FRAIM tokens before returning sanitized text.
- The other cited files contain Git/platform utilities, project setup, installer, cookie, marketplace, or connectivity-check code; inspection found no concrete attack behavior in them.
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.284.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.284 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.