fraim@2.0.337
FRAIM core CLI and MCP package.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected source does not establish malicious behavior. The telemetry and agent setup are product features reached through explicit CLI commands, with metrics directed to a loopback receiver.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
No malicious trigger was found; the relevant configuration changes follow explicit FRAIM CLI commands.
Impact
No confirmed attack impact was identified.
Mechanism
The reviewed setup configures FRAIM-owned agent artifacts and local metrics collection; no harmful behavior was established.
AI rationale
The inspected source does not establish malicious behavior. The telemetry and agent setup are product features reached through explicit CLI commands, with metrics directed to a loopback receiver.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json specifies the CLI entry points; the inspected manifest contains no lifecycle scripts.
- Explicit init-project and add-ide commands configure Claude metrics, filling missing settings and directing OTLP to a loopback receiver.
- The local receiver binds to 127.0.0.1 and handles token metric snapshots locally.
- Agent integration writes FRAIM-named artifacts, and project adapters reject writes outside the project root.
- The flagged utilities perform diagnostic checks, repository inspection, local overrides, or package setup; no concrete malicious action was identified.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
16 flagged · loading sourcedist/src/core/utils/git-utils.jsView file
9exports.sanitizeRepoIdentifier = sanitizeRepoIdentifier;
L10: const child_process_1 = require("child_process");
L11: function extractLocalFolderLabel(rawPath) {
High
Child Process
Package source references child process execution.
dist/src/core/utils/git-utils.jsView on unpkg · L9dist/src/cli/doctor/checks/scripts-checks.jsView file
235// Primary probe: py launcher (not subject to App Execution Alias)
L236: const pyResult = (0, child_process_1.spawnSync)('py --version', { timeout: 1500, encoding: 'utf8', shell: true, windowsHide: true });
L237: if (pyResult.status === 0) {
High
Shell
Package source references shell execution.
dist/src/cli/doctor/checks/scripts-checks.jsView on unpkg · L235bin/fraim.jsView file
Findings
1 Critical13 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/src/cli/doctor/checks/mcp-connectivity-checks.js
HighChild Processdist/src/core/utils/git-utils.js
HighShelldist/src/cli/doctor/checks/scripts-checks.js
HighSandbox Evasion Gated Capabilitydist/src/cli/commands/override.js
HighTrigger Reachable Persistencedist/src/cli/utils/persist-shell-path.js
HighRuntime Package Installdist/src/cli/setup/user-level-sync.js
HighSemantic Analysis Limiteddist/src/cli/utils/managed-agent-install.js#virtual:normalized:round1
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Similaritydist/src/cli/commands/override.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to fraim@2.0.337.
See all versions of fraim for other recorded verdicts.
- Review the evidence and your use of fraim@2.0.337 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.