opik@2.2.130
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe scanner’s high-risk indicators correspond to user-invoked CLI analytics and a uv subprocess, not observed command-output collection or credential transfer. The analytics destination is Comet’s stats service, its payload contains invocation metadata, and the user can disable it; no install hooks are declared.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the opik CLI.
Impact
The inspected code does not establish credential theft, command-output exfiltration, or an unrequested system change.
Mechanism
The CLI reports session and command metadata, platform details, and CI status; analytics can be disabled. It launches uv with inherited standard input, output, and error streams.
AI rationale
The scanner’s high-risk indicators correspond to user-invoked CLI analytics and a uv subprocess, not observed command-output collection or credential transfer. The analytics destination is Comet’s stats service, its payload contains invocation metadata, and the user can disable it; no install hooks are declared.
Evidence
package.jsondist/cli.js
Network endpoints1
stats.comet.com/notify/event/
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the SDK and CLI entrypoints and declares no install lifecycle hooks.
- The CLI sends invocation analytics to Comet’s stats endpoint; analytics can be disabled, and the reported fields are session, command, version, platform, and CI metadata.
- The CLI hands off to uv with inherited stdio; inspected SDK and dependency excerpts show ordinary SDK, type, formatting, and provider code.
Evidence against
- The CLI’s analytics default is enabled and its payload includes the parsed command and flags, but the user invokes the CLI and can disable analytics.
- Static alerts flag command execution and network behavior, but the CLI only checks uv’s version and launches the configured MCP tool; it does not read command output for transmission.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flaggeddist/cli.jsView file
1Source sends the broad process environment to a literal external destination.
L1: #!/usr/bin/env node
L2: import {spawnSync}from'child_process';import {chalkStderr}from'chalk';import {randomBytes,createHash}from'crypto';import U,{accessSync,constants}from'fs';import _ from'os';import i...
L3: ${chalkStderr.red("\u2717")} ${chalkStderr.bold("The Opik MCP configuration requires uv, which is not installed on this machine.")}
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L11#!/usr/bin/env node
L2: import {spawnSync}from'child_process';import {chalkStderr}from'chalk';import {randomBytes,createHash}from'crypto';import U,{accessSync,constants}from'fs';import _ from'os';import i...
L3: ${chalkStderr.red("\u2717")} ${chalkStderr.bold("The Opik MCP configuration requires uv, which is not installed on this machine.")}
High
1#!/usr/bin/env node
L2: import {spawnSync}from'child_process';import {chalkStderr}from'chalk';import {randomBytes,createHash}from'crypto';import U,{accessSync,constants}from'fs';import _ from'os';import i...
L3: ${chalkStderr.red("\u2717")} ${chalkStderr.bold("The Opik MCP configuration requires uv, which is not installed on this machine.")}
Findings
1 Critical5 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighTrigger Reachable Command Output Exfiltrationdist/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to opik@2.2.130.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.130 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.