opik@2.2.134
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI performs undisclosed, default-on runtime telemetry to the vendor endpoint, so this merits a warning under the telemetry rule. The inspected events contain usage metadata and do not establish credential or content exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the opik CLI, before it checks for uv and hands off or reports that uv is missing.
Impact
Usage activity is reported to the package vendor without an in-package disclosure. The inspected payload does not show credential or file-content collection.
Mechanism
Posts event metadata to stats.comet.com. The identifier is based on the configured Opik workspace or a hash of the host name and username; events include filtered command and flag names and runtime details. OPIK_ANALYTICS_ENABLE disables reporting.
AI rationale
The CLI performs undisclosed, default-on runtime telemetry to the vendor endpoint, so this merits a warning under the telemetry rule. The inspected events contain usage metadata and do not establish credential or content exfiltration.
Evidence
dist/cli.js
Network endpoints1
stats.comet.com/notify/event/
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The CLI sends analytics to the default Comet endpoint, stats.comet.com/notify/event/.
- Analytics is enabled by default; OPIK_ANALYTICS_ENABLE can disable it.
- Events include an anonymous ID, command and flag names, SDK and Node versions, platform, architecture, and CI status.
- The CLI tracks invocation and flushes events when it hands off to uv or reports that uv is missing.
Evidence against
- The payload contains usage metadata rather than credentials, file contents, or command output.
- The CLI provides an environment variable to disable analytics and another to override the analytics URL.
- The package manifest identifies this file as the opik CLI entry point; no install-time telemetry hook is declared.
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.134.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.134 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.