opik@2.2.127
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the reviewed CLI telemetry targets Comet and supports an opt-out. The SDK’s default endpoint and host-derived client identifier are consistent with its stated service; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json routes imports to SDK bundles and the CLI, with no install lifecycle hook.
- CLI analytics sends invocation metadata to Comet’s stats endpoint and can be disabled with OPIK_ANALYTICS_ENABLE.
- The SDK defaults to Comet’s Opik API; its client identifier is derived from the local hostname and username.
- The inspected dependencies expose terminal styling, INI parsing, and Anthropic provider functionality through package entrypoints.
- The inspected SDK entrypoints re-export library APIs; no separate attack behavior was identified.
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.127.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.127 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.