golang-popular-librarieslisted

# Choose a Go Library Make a requirement-driven decision, not a popularity ranking. The best outcome may be the standard library, an existing dependency, a small local implementation, or no change. ## Define the requirement Before searching, establish: - required behavior and excluded scope; - library versus application usage; - expected scale, latency, reliability, and security constraints; - supported Go versions, platforms, and CGO policy; - public API, serialization, storage, and interoperability constraints; - license and maintenance requirements; - the repository's existing dependencies and architectural conventions. If a missing choice would materially change the recommendation, present it instead of assuming a framework or vendor. ## Build candidates from live evidence Start with the standard library and modules already present in go.mod. Add external candidates only when they offer material value. For each external candidate, inspect current authoritative sources: - pkg.go.dev module and package pages; - canonical repository and tagged releases; - versioned documentation and migration guides; - license files; - Go vulnerability database entries; - module graph and Go-version requirements. Use recent activity, maintainer response, release discipline, test evidence, and documented compatibility as signals. Stars, dependents, and name recognition are secondary context, not selection criteria. Record when evidence was checked because library status changes. Ex