golang/vgo
[mirror] Versioned Go Prototype observed · 2026-08-28
Health v2 · maintenance only
73/100
- Activity 91
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3116
- days_rel: n/a
- days_push: 54
- n_releases_24m: 0
Adoption not part of the score
1509 stars · 62 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A standalone prototype of a version-aware `go` command that brought Go 1.11 module support to users on Go 1.10 toolchains. It is now obsolete, as all of its features were incorporated into the main Go toolchain.
Use cases
- manage Go project dependencies with semantic versioning on Go 1.10
- try out Go modules before upgrading to Go 1.11
- experiment with versioned Go workflows
- resolve and download specific versions of Go packages
When to choose
- you are stuck on a Go 1.10 toolchain and need module support (historical scenario only)
- you are studying the history of Go's module system design
When to avoid
- you use Go 1.11 or later - modules are built into the standard `go` command
- you are starting a new project
- you need maintained tooling
Facets
cli-tool · maturity abandoned
package-manager build-tool cli developer-tools developer-tools version-control programming-languages go cross-platform cli go-modules dependency-management versioned-go obsolete historical command-line
1 source
- readme: https://github.com/golang/vgo · fetched 2026-08-28 · fff043a0ec31
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| golang/vgo | main | 73 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem