opik@2.2.107
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe scanner’s command-output and exfiltration indicators correspond to a uv version probe whose output is ignored and first-party CLI analytics containing usage metadata. The inspected manifest and runtime entrypoints support normal SDK and CLI behavior, with no malicious attack chain identified.
Decision evidence
public snapshot- The manifest exposes the SDK and CLI and has no install lifecycle hook; its listed scripts are development tasks.
- The CLI posts session, command and runtime metadata to Comet’s analytics endpoint when invoked; this is package-aligned telemetry.
- The CLI checks the installed uv version with output ignored, then passes the user’s arguments to the Opik runner.
- The inspected SDK entrypoints and declared dependency sources show ordinary SDK, formatting, configuration-parsing, and model-provider functionality.
- CLI analytics is enabled by default, though OPIK_ANALYTICS_ENABLE can disable it; reported fields include command, flags, and runtime details.
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.107.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.107 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.