@2digits/opencode-plugin@0.2.49
OpenCode plugin for PostHog LLM analytics integration
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe PostHog analytics purpose is disclosed, but the plugin automatically sends prompt and output content and a Git-derived identity using a built-in key. Because capture is on by default without explicit service configuration or opt-in, this is suspicious runtime telemetry.
Decision evidence
public snapshot- The plugin is enabled by default and sends events to PostHog’s EU endpoint unless configuration changes it.
- Captured generation events include the user prompt and model output; privacy mode removes these fields only when explicitly enabled.
- The plugin reads the local Git user email and uses it as the event identity when no distinct ID is configured.
- The package describes itself as an OpenCode plugin for PostHog LLM analytics, consistent with sending AI trace data to an analytics service.
- The plugin supports disabling capture with POSTHOG_OPENCODE_ENABLED=false and enabling privacy mode with POSTHOG_OPENCODE_LLMA_PRIVACY_MODE=true.
Source & flagged code
3 flaggedThe plugin is enabled by default and sends events to PostHog’s EU endpoint unless configuration changes it.
dist/index.mjsView on unpkg · L2Captured generation events include the user prompt and model output; privacy mode removes these fields only when explicitly enabled.
dist/index.mjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @2digits/opencode-plugin@0.2.49.
See all versions of @2digits/opencode-plugin for other recorded verdicts.
- Review the evidence and your use of @2digits/opencode-plugin@0.2.49 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.