opik@2.2.96
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection shows package-aligned launcher telemetry and an Opik tool handoff, with no install lifecycle hook or confirmed attack behavior. The scanner’s credential and record exfiltration claims are not supported by the inspected CLI payload.
Decision evidence
public snapshot- The manifest points to the SDK entrypoints and CLI; its scripts define no install lifecycle hook.
- The CLI sends launcher event metadata to Comet analytics. Its default endpoint is stats.comet.com, and analytics can be disabled with an environment setting.
- The scanner alleges credential and application-record exfiltration, but the inspected CLI payload contains launcher, command, platform, and version metadata; no credential or application-record collection is shown.
Source & flagged code
8 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L1This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to opik@2.2.96.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.96 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.