opik@2.2.124
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s execution and network indicators resolve to the user-invoked CLI, which checks for uv and hands off to the Opik tool while sending package analytics. The SDK uses configured Opik credentials and service URLs; the inspected source does not establish a malicious attack surface.
Decision evidence
public snapshot- The manifest maps the package to SDK entrypoints and a CLI. Its listed scripts are build, lint, typecheck, formatting, and test tasks; there is no install lifecycle hook.
- The SDK bundles read OPIK_API_KEY and OPIK_URL_OVERRIDE as client configuration, consistent with sending authenticated requests to the configured Opik service.
- The CLI sends Comet analytics when invoked. Its events contain a hashed host and user identifier plus command and platform metadata; analytics can be disabled, and the source shows no command output in the event fields.
- The inspected dependency manifests and entry files map to terminal styling, INI parsing, and an Anthropic provider; no attack behavior was identified in those excerpts.
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.124.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.124 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.