opik@2.2.120
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected source shows default-on, opt-out usage telemetry to the package vendor, which is package-aligned behavior. The payload includes a stable hash of the hostname and username, but the source does not establish credential theft or another concrete attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the opik CLI invokes the telemetry path.
Impact
The vendor receives CLI usage and platform metadata with a stable hashed machine and user identifier. No credential transfer or unrelated destructive action was established.
Mechanism
The CLI posts usage events to stats.comet.com; analytics can be disabled with OPIK_ANALYTICS_ENABLE.
AI rationale
The inspected source shows default-on, opt-out usage telemetry to the package vendor, which is package-aligned behavior. The payload includes a stable hash of the hostname and username, but the source does not establish credential theft or another concrete attack.
Evidence
dist/cli.js
Network endpoints1
stats.comet.com/notify/event/
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json routes the library to its SDK bundles and exposes dist/cli.js as the opik command; the inspected bundle and type files are consistent with those entrypoints.
- The CLI sends usage events to stats.comet.com. Collection is enabled by default but can be disabled with OPIK_ANALYTICS_ENABLE; the payload contains a hashed host and username identifier plus command, flags, runtime, platform, and CI metadata.
- The CLI hands off to uv to run the Opik tool. The inspected dependency files are ordinary library modules, and no concrete credential theft or unrelated destructive behavior was identified.
- The style-application function returns the input string surrounded by openAll and closeAll sequences.
Evidence against
- Default-on telemetry sends a stable hash derived from the local hostname and username, along with CLI usage metadata, to the vendor’s analytics endpoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.120.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.120 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.