opik@2.2.95
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected SDK entrypoints expose ordinary Opik APIs using Comet’s service. The CLI’s observed outbound request is package-aligned telemetry triggered by CLI invocation; source inspection did not support the scanner’s credential or command-output exfiltration claims.
Decision evidence
public snapshot- package.json exposes the SDK and CLI; its scripts are build, lint, type-check, formatting, and test commands, with no install lifecycle hook.
- dist/index.cjs defaults the SDK API to Comet’s Opik service and reads its API key from configuration.
- dist/index.d.ts exports SDK tracing, evaluation, and client APIs consistent with the package description.
- The CLI sends invocation metadata to Comet’s statistics endpoint; analytics can be disabled with OPIK_ANALYTICS_ENABLE.
- The CLI’s network activity is triggered by invoking the command, which checks for uv and hands off to `uv tool run opik`. No credential or command-output transfer was found.
Source & flagged code
7 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.95.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.95 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.