opik@2.2.123
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe scanner’s command execution and network indicators correspond to the CLI’s uv handoff and Comet usage telemetry. Inspected source shows no install hook or concrete attack behavior, so the package is clean.
Decision evidence
public snapshot- package.json exposes the CLI and SDK entrypoints and contains no install lifecycle hook.
- The CLI sends usage events to Comet’s telemetry host; the event contains command and flag summaries, session and SDK details, and platform metadata.
- Telemetry can be disabled with OPIK_ANALYTICS_ENABLE set to 0, false, or no; workspace identity uses a configured value or a hostname hash.
- The SDK bundle and its type declarations expose SDK functionality and imports; the inspected dependency excerpts show ordinary terminal styling, INI parsing, and Anthropic provider code.
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.123.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.123 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.