opik@2.2.136
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends undisclosed, default-on runtime telemetry to the vendor’s analytics endpoint, including a configured workspace identifier. This is a privacy risk, but the reviewed flow is limited to CLI usage metadata and does not establish credential theft or another malicious attack.
Decision evidence
public snapshot- The CLI enables analytics by default; OPIK_ANALYTICS_ENABLE can disable it.
- On CLI invocation, analytics includes a workspace value as anonymous_id, using OPIK_WORKSPACE or the workspace read from ~/.opik.config; otherwise it derives an ID from hostname and username.
- The CLI posts event data to stats.comet.com, including command names, flag names, runtime version, OS, architecture, and CI status.
- The package README has no mention of analytics, based on searches for “analytics” and “OPIK_ANALYTICS”.
- Analytics runs when a user invokes the CLI, not during installation or package import.
- The CLI records only command and flag names, not their values; the reviewed payload does not include credentials or command output.
- An environment variable allows users to disable analytics.
Source & flagged code
9 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.136.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.136 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.