Skip to content

Run govulncheck

Run govulncheck #144

Triggered via schedule January 29, 2026 12:11
Status Failure
Total duration 44s
Artifacts

govulncheck.yaml

on: schedule
govulncheck
41s
govulncheck
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 warning
govulncheck
Process completed with exit code 3.
govulncheck
server.IDPServer.ServeHTTP calls http.HandlerFunc.ServeHTTP, which eventually calls tls.Dialer.DialContext
govulncheck
server.ServeOnLocalTailscaled calls fmt.Printf, which eventually calls tls.Conn.Write
govulncheck
verifier.main calls io.ReadAll, which eventually calls tls.Conn.Read
govulncheck
tsidp.main calls http.Server.Serve, which eventually calls tls.Conn.HandshakeContext
govulncheck
tsidp.main calls http.Server.Serve, which eventually calls tls.Conn.Handshake
govulncheck
verifier.main calls url.URL.Query
govulncheck
server.TestScopeHandling calls url.ParseQuery
govulncheck
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.