Closing as intentional: the ws:// here is the Chrome DevTools Protocol connection to the internal headless-Chrome container (CHROME_WS_URL) used for PDF rendering. It never leaves the internal Docker network and the URL is config-driven — wss:// can be used if the deployment provides it.
Closing as intentional: the `ws://` here is the Chrome DevTools Protocol connection to the internal headless-Chrome container (`CHROME_WS_URL`) used for PDF rendering. It never leaves the internal Docker network and the URL is config-driven — `wss://` can be used if the deployment provides it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
high Finding
Scanner: semgrep
Severity: high
Rule: javascript.lang.security.detect-insecure-websocket.detect-insecure-websocket
Description
Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections.
Location
File:
/tmp/compliance-scanner/repos/Compliance Scanner/compliance-agent/src/pentest/report/pdf.rs(line 62)Code
Fingerprint:
cdd662ca6394f15d7b19ee19c90232ca5a0a697bcd0226b27828e43f8abcc85bGenerated by compliance-scanner
Labels: severity:high, scanner:semgrep, compliance-scanner
Closing as intentional: the
ws://here is the Chrome DevTools Protocol connection to the internal headless-Chrome container (CHROME_WS_URL) used for PDF rendering. It never leaves the internal Docker network and the URL is config-driven —wss://can be used if the deployment provides it.