gomods/athens

A Go module datastore and proxy

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Type:Server / PlatformCategory(s):Build Systems & Package ManagersDeveloper Tools
Added to GitGenius on September 14th, 2026
Created on February 25th, 2018
Open Issues & Pull Requests: 151 (+0)
GitHub issues: Enabled
Number of forks: 544
Total Stargazers: 4,798 (+0)
Total Subscribers: 95 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.0 days
Mean response time: 122.9 days
90th percentile: 509.6 days
Tracked items: 55

Most active contributors

Sign in to see contributor activity.

How this project is maintained

92% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 961 days
Stale 30+ days: 18
Stale 90+ days: 17

Recent activity

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

Top labels

  • enhancement (6)
  • good first issue (6)
  • bug (4)
  • question (4)
  • help wanted (3)
  • proposal (3)
  • docs (2)
  • duplicate (2)

Most active issues this week

Detailed Description

Athens is a Go module proxy and datastore that implements the Go Module proxy protocol for enterprise use.

The tool solves the problem of managing Go module dependencies in organizations by acting as a caching proxy between developers and the public Go module registry. It intercepts module download requests, stores modules locally, and serves them from configurable storage backends. This approach allows teams to control their dependency supply chain, ensure offline availability of modules, and reduce load on public registries. Athens supports multiple storage backends including cloud blob storage, MongoDB, content distribution networks, shared disk, and in-memory storage, making it adaptable to different infrastructure setups.

Teams should adopt Athens if they need centralized control over Go module dependencies within their organization or want to reduce reliance on external module sources. It suits development workflows where teams run their own proxy servers configured to their infrastructure and security requirements. The tool is production-ready, with development teams at several companies already using it in their everyday workflows.

The project is actively seeking new core maintainers to sustain its development. The codebase welcomes contributions across technical challenges, documentation, and release management, with a documented contribution process for both experienced and new open source contributors. Development documentation and contribution guidelines are maintained to help people get involved.