golang-pkg-go-devlisted

# Explore Published Go Packages Answer package questions from current, attributable evidence. `godig` is the preferred interface when its CLI or MCP operations are already available because it exposes focused pkg.go.dev queries. Direct official sources remain the fallback and the authority for ambiguous results. ## Define the target Identify: - the package import path and containing module path; - the requested facet: API, examples, version, dependencies, license, importers, or vulnerabilities; - the caller's Go version and platform when build constraints matter; - the version selected by a local repository. For a local project, read `go.mod`, `go.work`, `replace` directives, and imports first. Record the selected module version before comparing it with published documentation. ## Choose the interface | Question | Best starting point | | --- | --- | | Published docs, examples, versions, licenses, importers | `godig` or pkg.go.dev | | Exact dependency source selected by `go.mod`, including replacements | gopls or the local module cache | | Local definitions, references, implementations, or rename impact | gopls/LSP | | Reachable vulnerabilities in the current application | `govulncheck` or an equivalent workspace reachability check | | Library comparison or adoption decision | Live package evidence followed by a separate trade-off analysis | When `godig` is present, inspect `godig --help` and the relevant subcommand help because its command surface is versioned. Start