Golang Package Version History And Release Tracking

via “golang-package-version-history-and-release-tracking”

** - MCP server to provide golang packages and their information from pkg.go.dev

Unique: Surfaces golang package version history and release metadata through MCP, allowing LLM agents to make informed version selection decisions based on release timelines and stability indicators

vs others: Provides structured version history lookup vs. requiring agents to manually inspect pkg.go.dev or parse go.mod version constraints, enabling automated version compatibility analysis

via “package version history and release timeline retrieval”

** - Search and get up-to-date information about NPM, Cargo, PyPi, and NuGet packages.

Unique: Normalizes version schema differences across four ecosystems (semver, PEP 440, NuGet versioning) into a unified timeline format with registry-specific metadata like yanked status, enabling cross-registry version comparison without manual schema translation

vs others: Handles version history across multiple ecosystems in one call, whereas npm-check-updates and similar tools are language-specific and require separate queries per registry