fraim@2.0.314
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The scanner similarity labels were not supported by the inspected source; the telemetry setup enables local token metrics through CLI setup flows.
Decision evidence
public snapshot- The manifest points to CLI entrypoints and defines no install lifecycle hook.
- CLI setup can enable Claude token telemetry globally, but it targets a local receiver that parses token usage metrics; setup preserves existing settings.
- IDE integration and project adapters install FRAIM-specific artifacts at named locations.
- Git metadata checks, override path validation, and first-run PATH setup are tied to CLI behavior.
- User-level dependencies, managed agent installs, organization snapshots, and GitHub workflow sync have bounded setup or repository roles.
- Installer templates, marketplace validation, session cookies, diagnostic sanitization, and MCP connectivity checks show no confirmed attack behavior.
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.314.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.314 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.