fraim@2.0.288
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged agent setup and telemetry behavior is reached through user-invoked setup flows. The inspected source did not establish concrete malicious behavior; the scanner similarity labels alone do not support a malicious verdict.
Decision evidence
public snapshot- package.json defines CLI entrypoints and contains no install lifecycle scripts; index.js dispatches to the CLI.
- Agent setup writes FRAIM discovery files during onboarding or user-invoked setup and sync.
- Claude Code telemetry is enabled by the add-IDE command and targets a local proxy.
- Inspected diagnostic, Git, installer, cookie, marketplace, and connectivity helpers show product operations; no concrete attack behavior was identified.
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.288.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.288 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.