opik@2.2.125
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner's command-output exfiltration label is not supported by the CLI source: its telemetry contains bounded invocation metadata, while the uv handoff inherits standard streams. The observed network use is consistent with Comet's product telemetry and Opik API, and the manifest has no install hook.
Decision evidence
public snapshot- package.json exposes a library and CLI and lists no install lifecycle script.
- The CLI sends limited command and platform metadata to Comet telemetry; collection is enabled by default and can be disabled with OPIK_ANALYTICS_ENABLE.
- The CLI passes invocation arguments to uv tool run opik with inherited standard streams; the subprocess is not used to capture command output for telemetry.
- The SDK reads its API key and URL from caller configuration or environment variables and defaults to Comet's Opik API.
- The cited dependency files contain terminal styling imports, an INI encoder, and an Anthropic provider module that imports API-key helpers.
Source & flagged code
6 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to opik@2.2.125.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.125 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.