The CLI automatically syncs audit reports and source snippets to the package’s dashboard during a default scan, even though syncing is presented as an option. This is a real privacy risk, but the destination is the package’s own service and the reviewed code did not establish credential theft or an unrelated collector.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI scan, including with JSON output; syncing defaults to enabled.
Impact
Project findings and code snippets leave the local environment without a separate sync request; existing dashboard issue rows may also be replaced.
Mechanism
The CLI posts the audit report to capsalock.vercel.app and uses a fixed Supabase endpoint to delete matching issue rows and write refreshed report data.
Evidence
bin/capsalock.jsbin/cliEntrypoint.js
Network endpoints2
capsalock.vercel.appeyiuhwcriwyfwzhdpcba.supabase.co