opik@2.2.87
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected entrypoints show package-aligned SDK and explicit CLI behavior without an install-time attack chain. Configurable authentication and limited telemetry do not establish malicious exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Users import the SDK or invoke the opik CLI; no automatic install hook is declared.
Impact
No malicious mutation, credential theft, or covert execution was established from the inspected source.
Mechanism
The SDK uses configured authentication and endpoints, while the CLI launches Opik through uv and reports limited telemetry.
AI rationale
The inspected entrypoints show package-aligned SDK and explicit CLI behavior without an install-time attack chain. Configurable authentication and limited telemetry do not establish malicious exfiltration.
Evidence
.opik.config
Network endpoints2
stats.comet.com/notify/event/www.comet.com/opik/api
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares SDK entrypoints and an explicit CLI, with no install lifecycle hooks or runtime self-dependency.
- The CLI explicitly invokes uv to run Opik with the user's command arguments.
- CLI telemetry contains workspace identity and command metadata rather than credentials or argument values.
- SDK authentication uses the configured API key and API endpoint; caller options override environment and file configuration.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 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 {randomUUID,createHash}from'crypto';import C,{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 · L1•matchType = previous_version_dangerous_delta
matchedPackage = opik@2.2.86
matchedIdentity = npm:b3Bpaw:2.2.86
similarity = 0.833
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg1#!/usr/bin/env node
L2: import {spawnSync}from'child_process';import {chalkStderr}from'chalk';import {randomUUID,createHash}from'crypto';import C,{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
2 Critical6 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
CriticalPrevious Version Dangerous Deltadist/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
Low
Affected versions and remediation
This report applies to opik@2.2.87.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.87 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.