opik@2.2.114
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged CLI behavior is user-triggered Comet analytics plus an argument-forwarding handoff. Inspected SDK and dependency excerpts support ordinary package functionality rather than the scanner's command-output exfiltration claim.
Decision evidence
public snapshot- package.json exposes the SDK entrypoints and CLI; its scripts contain no install lifecycle hook.
- dist/cli.js sends CLI usage events to Comet analytics when invoked; analytics can be disabled with OPIK_ANALYTICS_ENABLE.
- The CLI checks for uv and forwards the user's arguments to the Opik tool.
- The bundled SDK and inspected dependency sources show ordinary SDK, attachment, terminal styling, INI, and Anthropic provider code.
- The CLI performs default-on telemetry, but the inspected source sends usage metadata to the package-aligned Comet analytics endpoint.
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.114.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.114 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.