Skip to content

feat: Authorization command to use implicit flow #187

feat: Authorization command to use implicit flow

feat: Authorization command to use implicit flow #187

Triggered via pull request June 3, 2026 11:00
Status Failure
Total duration 1m 17s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
govulncheck
Process completed with exit code 3.
govulncheck
ims.Config.AuthorizeJWTExchange calls fmt.Sprintf, which eventually calls x509.HostnameError.Error
govulncheck
ims.Config.AuthorizeImplicit calls fmt.Fprintf, which eventually calls x509.Certificate.VerifyHostname
govulncheck
ims.Config.AuthorizeImplicit calls fmt.Fprintf, which eventually calls x509.Certificate.Verify
govulncheck
ims.startCaptureServer calls http.Server.Serve, which eventually calls textproto.Reader.ReadMIMEHeader
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
govulncheck
Failed to restore: Cache service responded with 400
govulncheck
Both go-version and go-version-file inputs are specified, only go-version will be used