The package’s dashboard sync is part of its stated product function, and the reviewed source does not substantiate the credential or metadata theft hints. However, ordinary scans synchronize by default and the sync path deletes existing dashboard issue rows, creating a meaningful destructive-action risk without an explicit sync request.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user runs the capsalock scan command; synchronization is enabled by default and can be disabled with --no-sync.
Impact
Existing dashboard issue state or records can be lost or reset during an ordinary scan without an explicit --sync request.
Mechanism
The CLI sends audit data to the CapsaLock dashboard and Supabase, deletes issue rows for matched repository IDs, then inserts replacement rows.
Evidence
bin/cliEntrypoint.js/api/db-audit-report/rest/v1/01_issues/rest/v1/02_repositories
Network endpoints2
capsalock.vercel.appeyiuhwcriwyfwzhdpcba.supabase.co