feat(loo-4729): api-key command
#2
notnmeyerAnnotations
10 errors and 1 warning
|
vuln
api.Client.GetAPIKey calls http.http2transportResponseBody.Close, which eventually calls tls.Conn.Write
|
|
vuln
api.Client.GetAPIKey calls http.body.Close, which eventually calls tls.Conn.Read
|
|
vuln
api.Client.GetAPIKey calls http.Client.Do, which eventually calls tls.Conn.HandshakeContext
|
|
vuln
api.Client.GetAPIKey calls http.Client.Do, which eventually calls tls.Dialer.DialContext
|
|
vuln
api.Client.GetAPIKey calls http.http2transportResponseBody.Close, which eventually calls tls.Conn.Write
|
|
vuln
api.Client.GetAPIKey calls http.body.Close, which eventually calls tls.Conn.Read
|
|
vuln
api.Client.GetAPIKey calls http.Client.Do, which eventually calls tls.Conn.HandshakeContext
|
|
vuln
api.Client.GetAPIKey calls http.Client.Do, which eventually calls url.URL.Parse
|
|
vuln
api.Client.GetAPIKey calls http.Client.Do, which eventually calls url.Parse
|
|
vuln
api.Client.GetAPIKey calls http.cancelTimerBody.Close, which eventually calls os.ReadDir
|
|
vuln
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|