opik@2.2.116
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found default-on, opt-out CLI analytics to the package vendor's endpoint, activated by user invocation. The inspected payload and runtime behavior do not establish malicious exfiltration or another concrete attack.
Decision evidence
public snapshot- package.json maps the SDK and CLI entrypoints and lists build and test scripts; no install lifecycle hook is declared.
- The CLI records invocation and UV status, sends command and flag summaries with runtime metadata to Comet analytics, and allows telemetry to be disabled with OPIK_ANALYTICS_ENABLE.
- The CLI hands the user's arguments to uv to run Opik; its inspected code does not send command output or credentials.
- The SDK entrypoints and inspected dependency sources align with SDK, provider, configuration parsing, and terminal formatting functions.
- The scanner's broad exfiltration label is not supported by the inspected CLI payload, which contains command and flag summaries and runtime metadata, not credentials or rich application records.
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.116.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.116 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.