The flagged host and credential patterns are scanner examples or functional requests: GitHub tokens accompany remote GitHub repository downloads, and report data is sent to CapsaLock only when the user passes --sync. The automatic npm registry request checks the package version and does not include user data.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
CLI invocation; report syncing requires the explicit --sync option, and GitHub credentials are used for remote repository downloads.
Impact
These requests match the scanner's functions; no credential exfiltration or unrelated data collection was identified.
Mechanism
The CLI sends GitHub credentials to the GitHub snapshot URL when downloading a remote repository. With --sync, it sends findings to the CapsaLock endpoint or the configured CAPSALOCK_API_BASE. The version check requests CapsaLock's version from the npm registry.
Evidence
bin/capsalock.jsbin/cliEntrypoint.js
Network endpoints4
github.comapi.osv.devregistry.npmjs.org