fraim@2.0.318
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner similarity labels were not evidence of malicious behavior. Inspected code showed explicit CLI setup for FRAIM integrations and local telemetry, with no concrete attack behavior established.
Decision evidence
public snapshot- package.json points to the CLI entrypoints; inspected runtime behavior is invoked through those entrypoints.
- Claude telemetry settings use a localhost endpoint and are written by the explicit add-IDE and project-init commands.
- Agent integration code installs FRAIM invocation artifacts; the inspected diagnostic code redacts known secrets.
- The inspected git, workflow, installer, marketplace, and platform utilities serve product operations; no concrete attack behavior was identified.
- The cookie service configures FRAIM session cookies, and the connectivity check is part of the FRAIM doctor command.
- No lifecycle script is declared in the inspected package manifest.
- The telemetry configuration is activated by explicit CLI commands and targets a local receiver; the inspected excerpts show no unrelated credential recipient.
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.318.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.318 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.