skopeo/vendor/golang.org/x/oauth2
renovate[bot] b78a415987 fix(deps): update module github.com/containers/image/v5 to v5.34.0
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
2025-01-31 21:34:59 +01:00
..
internal Update c/image after https://github.com/containers/image/pull/2408 2024-05-14 00:27:15 +02:00
.travis.yml Add support for Fulcio and Rekor, and --sign-by-sigstore=param-file 2023-01-14 13:33:57 +01:00
CONTRIBUTING.md Add support for Fulcio and Rekor, and --sign-by-sigstore=param-file 2023-01-14 13:33:57 +01:00
deviceauth.go Update c/image and c/common to latest 2023-11-16 18:21:43 +01:00
LICENSE fix(deps): update module github.com/containers/image/v5 to v5.32.1 2024-08-09 21:15:04 +00:00
oauth2.go fix(deps): update module github.com/containers/image/v5 to v5.34.0 2025-01-31 21:34:59 +01:00
pkce.go Update c/image and c/common to latest 2023-11-16 18:21:43 +01:00
README.md fix(deps): update module github.com/containers/image/v5 to v5.34.0 2025-01-31 21:34:59 +01:00
token.go fix(deps): update module github.com/containers/image/v5 to v5.33.0 2024-11-12 20:34:31 +01:00
transport.go Add support for Fulcio and Rekor, and --sign-by-sigstore=param-file 2023-01-14 13:33:57 +01:00

OAuth2 for Go

Go Reference Build Status

oauth2 package contains a client implementation for OAuth 2.0 spec.

See pkg.go.dev for further documentation and examples.

Policy for new endpoints

We no longer accept new provider-specific packages in this repo if all they do is add a single endpoint variable. If you just want to add a single endpoint, add it to the pkg.go.dev/golang.org/x/oauth2/endpoints package.

Report Issues / Send Patches

The main issue tracker for the oauth2 repository is located at https://github.com/golang/oauth2/issues.

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.

The git repository is https://go.googlesource.com/oauth2.

Note:

  • Excluding trivial changes, all contributions should be connected to an existing issue.
  • API changes must go through the change proposal process before they can be accepted.
  • The code owners are listed at dev.golang.org/owners.