The CLI defaults dashboard syncing to on, while its help presents syncing as an option. Because a normal scan can transmit code snippets and repository details to the publisher’s service without an explicit sync request, this is suspicious runtime telemetry, not demonstrated credential theft.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Running the CLI’s default `scan` command; `--no-sync` disables the behavior.
Impact
Project paths, code excerpts, and remediation details leave the local workspace without an explicit sync request; existing dashboard issue records may be replaced.
Mechanism
The CLI posts the audit report and issue records, including source snippets, to the dashboard and Supabase endpoints. It first deletes issue rows for matched repository IDs, then repopulates them.
Network endpoints2
capsalock.vercel.appeyiuhwcriwyfwzhdpcba.supabase.co