Finding Dependable Go Packages
summary
Practical checklist for picking Go packages: verify an acceptable license, check number of dependents (real users matter more than stars), read module-aware docs and examples, run tests locally and scan code for idiomatic Go and panics, inspect maintainer activity and issue turnaround, and prefer modules that follow import compatibility and semantic versioning. Use existing tools like godoc, the go command, Go Report Card and staticcheck. The Go team is building a module-aware discovery site that shows per-version docs, release history, imports and dependents and proposes a top-level score to simplify comparisons.
AI-written summary · about
chapters (11)
- 0:00Finding Dependable Go Packages
- 4:22How do I decide which package to use?
- 7:02Discovery Evaluation
- 9:11License
- 11:18Code Quality
- 14:24Upkeep
- 17:58If an old package and a new package have the same import path...
- 19:03Indirect Dependencies
- 20:20Should I use a third-party package at all?
- 21:42Maintenance
- 24:22How can we make this process better?
related talks
26mFinding Dependable Go Packages
24m"Finding Dependable Go Packages"
10m"Creating a Go Score for Module Discovery"
32mSecure and reliable development with Go
38mUsing Go Modules in everyday life
42mGo Module Hygiene: Keeping go.sum and go.mod in check
16mTools for working with Go Code
51mKeynote | State of the Go Nation