opik@2.2.137
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends runtime telemetry to Comet’s analytics host by default, and the package README does not disclose it. The inspected payload is limited to an identifier and CLI/runtime metadata, so this is suspicious telemetry rather than credential or command-output exfiltration.
Decision evidence
public snapshot- The package exposes dist/cli.js as the opik command.
- Each CLI invocation records an invocation event and detects whether uv is installed.
- CLI telemetry is enabled by default; OPIK_ANALYTICS_ENABLE can disable it.
- Events sent to the analytics endpoint include a workspace-derived anonymous ID and CLI metadata such as command, flags, runtime version, platform, architecture, and CI status.
- When no workspace is configured, the anonymous ID is derived by hashing the hostname and username.
- The telemetry runs when a user invokes the CLI; no install-time telemetry or import-time trigger was identified.
- The inspected event payload contains CLI metadata, not API keys, command output, or file contents.
- The CLI’s uv handoff matches the package’s documented purpose of providing Opik MCP configuration.
Source & flagged code
9 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.137.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.137 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.