opik@2.2.100
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime behavior aligns with the Opik SDK and launcher: vendor analytics on explicit CLI invocation and API use configured for Comet. The telemetry is default-enabled and includes a stable host-derived hash, but the inspected source does not establish an attack surface.
Decision evidence
public snapshot- package.json exposes dist/cli.js as a command and has no install lifecycle hook.
- The SDK uses the Comet Opik API by default, and its public client accepts configuration.
- When the CLI runs, it sends launcher events to Comet analytics with a hashed host and username plus command, flags, and runtime metadata; analytics can be disabled through an environment setting.
- The CLI checks for uv, reports if it is missing, and otherwise hands off to uv to run the Opik tool.
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.100.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.100 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.