opik@2.2.112
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe scanner’s exfiltration characterization is not substantiated: the inspected CLI sends package-aligned telemetry on user invocation, and its request body does not include command output or credentials. The SDK entrypoints and required dependency excerpts show normal library behavior, so the package is clean.
Decision evidence
public snapshot- package.json identifies this as the Opik SDK, routes its CLI to dist/cli.js, and lists no lifecycle hooks.
- The CLI sends launcher events to stats.comet.com when invoked, with analytics enabled by default but disableable through OPIK_ANALYTICS_ENABLE; event data is limited to command and flag names, runtime and platform details, CI status, and a hashed default workspace identifier.
- The inspected entrypoint and dependency excerpts show SDK exports and ordinary library code; the scanner’s command-output exfiltration claim is not supported by the inspected CLI source.
- CLI telemetry is enabled by default and includes command names, flags, and environment metadata; this is a privacy consideration, but the inspected recipient is the package vendor’s Comet telemetry host and the CLI must be invoked to send it.
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.112.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.112 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.