The Go Blog

Next steps for

Julie Qiu
31 January 2020


In 2019, we launched, a new hub for Go developers.

As part of the site, we also launched, a central source of information about Go packages and modules. Like, serves Go documentation. However, it also understands modules and has information about past versions of a package!

Throughout this year, we will be adding features to to help our users better understand their dependencies and help them make better decisions around what libraries to import.

Redirecting requests to

To minimize confusion about which site to use, later this year we are planning to redirect traffic from to the corresponding page on We need your help to ensure that addresses all of our users’ needs. We encourage everyone to begin using today for all of their needs and provide feedback.

Your feedback will inform our transition plan, with the goal of making our primary source of information and documentation for packages and modules. We’re sure there are things that you want to see on, and we want to hear from you about what those features are!

You can share your feedback with us on these channels:

As part of this transition, we will also be discussing plans for API access to We will be posting updates on Go issue 33654.

Frequently asked questions

Since our launch in November, we’ve received tons of great feedback about from Go users. For the remainder of this post, we thought it would be helpful to answer some frequently asked questions.

My package doesn’t show up on! How do I add it?

We monitor the Go Module Index regularly for new packages to add to If you don’t see a package on, you can add it by fetching the module version from See for instructions.

My package has license restrictions. What’s wrong with it?

We understand it can be a frustrating experience to not be able to see the package you want in its entirety on We appreciate your patience as we improve our license detection algorithm.

Since our launch in November, we’ve made the following improvements:

  • Updated our license policy to include the list of licenses that we detect and recognize
  • Worked with the licensecheck team to improve detection for copyright notices
  • Established a manual review process for special cases

As always, our license policy is at If you are having issues, feel free to file an issue on the Go issue tracker, or email so that we can work with you directly!

Will be open-sourced so I can run it at work for my private code?

We understand that corporations with private code want to run a documentation server that provides module support. We want to help meet that need, but we feel we don’t yet understand it as well as we need to.

We’ve heard from users that running the server is more complex than it should be, because it is designed for serving at public internet scale instead of just within a company. We believe the current server would have the same problem.

We think a new server is more likely to be the right answer for use with private code, instead of exposing every company to the complexity of running the internet-scale codebase. In addition to serving documentation, a new server could also serve information to goimports and gopls.

If you want to run such a server, please fill out this 3-5 minute survey to help us better understand your needs. This survey will be available until March 1st, 2020.

We’re excited about the future of in 2020, and we hope you are too! We look forward to hearing your feedback and working with the Go community on this transition.

Next article: Go 1.14 is released
Previous article: Proposals for Go 1.15
Blog Index