opik@2.2.122
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe scanner’s network and execution indicators resolve to user-invoked CLI telemetry and the expected Comet Opik API. No install hook or concrete malicious data transfer was found in the inspected source.
Decision evidence
public snapshot- package.json exposes the SDK and CLI and contains no install lifecycle hook; the listed scripts are development and build tasks.
- The CLI sends usage events when a user runs it. The payload contains a workspace or derived anonymous ID, command and flags, and runtime metadata; it does not include a provider API key.
- The telemetry defaults to Comet’s stats host and can be disabled with OPIK_ANALYTICS_ENABLE=0, false, or no. The SDK also defaults to Comet’s Opik API.
- The inspected dependency sources cover terminal formatting, INI parsing, and an Anthropic provider implementation; they do not show install-time behavior.
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.122.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.122 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.