opik@2.2.101
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe flagged network and process behavior is confined to user-invoked CLI analytics and a uv handoff for running Opik. The inspected source shows no credential or command-output exfiltration, and the package has no install lifecycle hook.
Decision evidence
public snapshot- package.json exports the library and CLI and defines no install lifecycle hook.
- The CLI posts launch telemetry to Comet’s stats endpoint; analytics can be disabled with OPIK_ANALYTICS_ENABLE.
- Telemetry contains launcher events and limited command, flag, runtime, platform, and workspace or hashed host identity fields; it does not include credentials or command output.
- The CLI hands off to uv to run Opik with inherited standard streams when the user invokes the command.
- The library entrypoint exports Opik client APIs; its declarations describe a configurable client.
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.101.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.101 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.