opik@2.2.109
Opik TypeScript and JavaScript SDK
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe flagged behavior is invocation-triggered analytics to the package’s own Comet endpoint, not an install-time beacon or credential transfer. The inspected entrypoints and required dependency source paths did not establish a malicious attack surface.
Decision evidence
public snapshot- package.json has no install lifecycle hook and maps the CLI to dist/cli.js; required runtime and dependency paths were inspected.
- The CLI sends invocation analytics to the package’s Comet statistics endpoint, with an environment variable that disables analytics.
- The analytics payload contains launcher and runtime metadata plus a limited command and flag summary; the CLI handoff runs the documented Opik tool through uv.
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.109.
See all versions of opik for other recorded verdicts.
- Review the evidence and your use of opik@2.2.109 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.