opik@2.2.128
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 8d ago · by lpm-firewall-aiStatic inspection found user-invoked telemetry to Comet’s stats endpoint, with an effective environment opt-out, and ordinary SDK traffic to its configured service. The scanner’s command-output concern is not supported: the CLI ignores output when checking for uv, and telemetry contains invocation metadata rather than subprocess output or credentials.
Decision evidence
public snapshot- package.json exposes a CLI and SDK entry points and declares no install lifecycle hook.
- The invoked CLI sends invocation metadata to Comet’s stats endpoint; analytics can be disabled with OPIK_ANALYTICS_ENABLE.
- The CLI checks for uv with output ignored, then hands off to the Opik tool with inherited standard streams.
- The SDK defaults to Comet’s API and uses its configured API key for authentication.
- The inspected provider dependency uses Anthropic’s API endpoint; inspected dependency manifests show build or test scripts, not install hooks.
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.128.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.128 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.