The CLI sends identifying GitHub repository and workflow/run metadata in default-on runtime analytics, which the README does not disclose. Because the recipient is Neon’s own analytics host and the behavior is opt-out, this is suspicious telemetry rather than malicious exfiltration.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A CLI invocation that records a successful command, when analytics are enabled; analytics are on by default and can be disabled with `--no-analytics` or `--analytics false`.
Impact
Neon analytics can associate CLI activity with a specific repository and CI run, exposing identifying CI/workspace metadata beyond what the README describes.
Mechanism
The success event includes GitHub environment values such as GITHUB_REPOSITORY, GITHUB_RUN_ID, and GITHUB_WORKFLOW_REF, then sends the event to Neon’s analytics host.
Evidence
dist/analytics.jsdist/env.jsREADME.md