The CLI defaults to syncing scan results, including source snippets and file paths, to the package's dashboard, while its help presents syncing as an option without clarifying it is already enabled. Because this is a stated package feature sending data to its own service, the issue warrants a warning for undisclosed runtime collection rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI's scan command; the manifest bin invokes runCli, and sync defaults to true.
Impact
Project code excerpts and audit details may leave the user's machine without an explicit sync request. The package's stated dashboard feature provides a legitimate reason for the transfer, so this is a disclosure and consent concern rather than clear data theft.
Mechanism
The CLI posts audit reports to capsalock.vercel.app and writes findings to a hard-coded Supabase project. Reports may include source snippets, paths, and suggested fixes.
Evidence
bin/capsalock.jsbin/cliEntrypoint.js
Network endpoints2
capsalock.vercel.appeyiuhwcriwyfwzhdpcba.supabase.co