fraim@2.0.295
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no npm lifecycle hooks, and the reviewed agent configuration writes occur through CLI setup flows and target FRAIM-owned files. Claude token metrics are routed through a local receiver into the configured FRAIM analytics flow; no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json defines CLI entrypoints and no npm lifecycle hooks.
- IDE integration writes FRAIM-named artifacts through CLI setup flows; project adapter writes are bounded to the project root.
- Claude telemetry is enabled in CLI setup flows and records token metrics through a loopback receiver; usage events go to the configured FRAIM analytics endpoint.
- Other inspected flagged files perform product operations such as diagnostics, git metadata handling, repository workflow setup, marketplace validation, and cookie management; no concrete attack behavior was found.
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.295.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.295 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.