opik@2.2.113
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe scanner’s command-output exfiltration hint is not borne out by the inspected CLI: it sends usage metadata and does not include captured command output or credentials. The observed telemetry is package-aligned and has an explicit environment-variable opt-out.
Decision evidence
public snapshot- package.json routes SDK imports and the CLI to dist files and lists build and maintenance scripts, with no install hook.
- Running the CLI builds usage events containing the command, flags, session, SDK and platform details, then sends them as JSON to the package telemetry endpoint.
- Analytics can be disabled with OPIK_ANALYTICS_ENABLE; the anonymous identifier uses a configured workspace or a hash of the hostname and username.
- The inspected runtime, type and dependency excerpts show SDK exports, provider integrations, terminal styling and INI parsing; they did not establish another exfiltration path.
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.113.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.113 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.