opik@2.2.108
⚠ Under reviewOpik TypeScript and JavaScript SDK
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected CLI telemetry sends invocation metadata to a Comet endpoint, and the scanner’s command-output and credential-exfiltration claims are not supported by that source. Several declared runtime dependencies remain source-unverified, so a clean verdict is not established.
Decision evidence
public snapshot- The manifest exposes the SDK bundle and a separate CLI entrypoint, with no install lifecycle hook shown.
- The CLI sends invocation metadata to Comet analytics; its event fields include command and flags, but no command output or credentials.
- The CLI’s child process runs `uv tool run opik` with inherited terminal output.
- Several declared runtime dependencies have metadata-only source coverage, leaving their behavior unresolved.
- The scanner’s claim that the reviewed CLI sends credentials or rich command output is not supported by its request body, which contains session and invocation metadata.
- The CLI analytics setting can be disabled with `OPIK_ANALYTICS_ENABLE=0`, `false`, or `no`.
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.108.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.108 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.