The CLI defaults to uploading repository identifiers and audit findings, including source snippets, to the vendor’s dashboard without an explicit sync request. This is an undisclosed runtime data upload, so it warrants a warning; the reviewed code does not establish credential theft or justify blocking the package.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI’s default scan command; --no-sync disables the upload.
Impact
Project names, finding details, file paths, and code excerpts can leave the local environment without the user explicitly requesting sync.
Mechanism
The scan report and issue data are sent over HTTPS to CapsaLock’s dashboard and Supabase backend.
Evidence
bin/capsalock.jsbin/cliEntrypoint.jsscanned project source files (file paths and finding snippets are included in the report)
Network endpoints2
capsalock.vercel.app/api/db-audit-reporteyiuhwcriwyfwzhdpcba.supabase.co