Go Module Proxy: Life of a Query
summary
Go modules get reproducible builds via minimal version selection, dependency fetches go through a configurable HTTP proxy (default proxy.golang.org), and a global checksum database provides signed tree heads and inclusion/consistency proofs so every client verifies sha256 gosum lines before trusting a module. The system uses a Merkle log backed by Trillian, tiles (client caches every 8th level) for proofs, and ships by default in Go 1.13 with proxy/comma-list and GOPRIVATE controls.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:14Solving build reproducibility
- 6:45Module proxies and caching
- 13:49Trusting source code
- 20:10Transparent checksum database
- 31:33Go 1.13 features
- 34:05Q&A
related talks
33mHow to Safely and Efficiently Build your App with Modules
17mPackage Management in Go: Under the Hood
31m"The Athens Project - A Proxy Server for Go Modules"
07mSecurity of Go Modules and Vulnerability Scanning in GoCenter
31mBring Sanity to your Dependencies
24m"Finding Dependable Go Packages"
07mBuilding A Central Go Modules Repository
26mFinding Dependable Go Packages
