opik@2.2.97
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe flagged CLI sends invocation metadata to the package's Comet analytics endpoint and hands off to uv with inherited output, so the source does not support the scanner's command-output exfiltration claim. The manifest lists no install hook, and no concrete malicious behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Invoking the opik CLI.
Impact
This supports package analytics; the inspected CLI does not capture child process output or transmit credentials.
Mechanism
The CLI posts invocation and runtime metadata to Comet's stats endpoint; an environment setting can disable analytics.
AI rationale
The flagged CLI sends invocation metadata to the package's Comet analytics endpoint and hands off to uv with inherited output, so the source does not support the scanner's command-output exfiltration claim. The manifest lists no install hook, and no concrete malicious behavior was identified.
Evidence
package.jsondist/cli.js
Network endpoints1
stats.comet.com/notify/event/
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and lists build and test scripts; no install hook appears.
- The CLI telemetry is enabled by default, can be disabled, and uses the Comet stats endpoint by default.
- Telemetry contains invocation and runtime metadata and is sent as a JSON POST.
- The CLI hands off to uv with inherited standard input and output; it does not capture child output.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
7 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 {createHash,randomBytes}from'crypto';import L,{accessSync,constants}from'fs';import f 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 {createHash,randomBytes}from'crypto';import L,{accessSync,constants}from'fs';import f 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 {createHash,randomBytes}from'crypto';import L,{accessSync,constants}from'fs';import f 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 Critical6 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighHost Fingerprint Exfiltrationdist/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.97.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.97 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.