golang/oauth2

Go OAuth2

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 11th, 2026
Created on April 14th, 2014
Open Issues & Pull Requests: 61 (+0)
GitHub issues: Enabled
Number of forks: 1,058
Total Stargazers: 5,897 (+0)
Total Subscribers: 120 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 116.9 days
Mean response time: 495.3 days
90th percentile: 1489.1 days
Tracked items: 120

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 1% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,122 days
Stale 30+ days: 25
Stale 90+ days: 22

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • endpoints (4)
  • dependencies (1)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

oauth2 is a Go client library that implements the OAuth 2.0 specification.

The library solves the problem of authenticating with OAuth 2.0 providers by offering a standardized client implementation. It handles the core OAuth 2.0 flows and token management, with built-in support for major providers like Google through provider-specific packages. The tool abstracts away the complexity of OAuth 2.0 protocol details, allowing developers to focus on integrating authentication into their applications.

Developers should adopt this library if they are building Go applications that need to authenticate users through OAuth 2.0 providers. It suits projects ranging from simple command-line tools to web services. The project has established a clear policy: new provider-specific packages are no longer accepted if they only add a single endpoint variable; instead, such endpoints should be contributed to the endpoints package. This keeps the repository focused and maintainable while still allowing community contributions for new providers.

The project maintains a substantial base of real-world adopters, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. However, issues and pull requests often wait weeks or longer for an initial response, indicating limited bandwidth for issue triage. The project requires all non-trivial contributions to be connected to an existing issue and mandates that API changes go through a formal proposal process before acceptance.