Individuals & short brands
Flat module
A single claim. The whole import path is the brand.
go get entiergo.org/uuid
go get entiergo.org/[email protected]Storefront · Discovery · Funding
The storefront for Go modules.
GitHub remains the workshop. EntierGo is where people find, trust, and support modules — prestige import paths like gonum.org or gvisor.dev, plus a catalog and funding layer the forge does not give you.
$ go get entiergo.org/uuidA vanity path alone is not the product.
github.com/user/mod already works. EntierGo exists only
if listing a module here is clearly better for
maintainers than GitHub-only.
EntierGo is the storefront, discovery, and funding layer for Go modules. Source stays on GitHub. This is where users find, trust, and support that work.
-
Workshop
Code, issues, pull requests, and semver tags live on GitHub under
github.com/entiergo/. We do not replace the forge. -
Storefront
Short brand paths, a searchable catalog, sponsor calls to action, trust signals, and author analytics live here — aimed at Go teams, not buried in a repo README.
How distribution works
One domain, two clients. Browsers get docs on pkg.go.dev.
go get gets source through the public proxy. We never
treat pkg.go.dev as a module proxy.
-
01
Claim & publish
Register a short module name or an org prefix. We sync to
github.com/entiergo/with the vanity path ingo.modand immutablevX.Y.Ztags. -
02
Vanity resolves
go gethits?go-get=1and receivesgo-importmeta pointing at GitHub. Browsers redirect to pkg.go.dev — the same experience as gVisor. That query is never redirected. -
03
The ecosystem delivers
proxy.golang.orgfetches,sum.golang.orgchecksums, and pkg.go.dev indexes docs. We do not host zips or run a custom docs site.
Two path shapes. First segment is exclusive.
Individuals take short names. Teams nest under an org — the same
model as npm unscoped versus scoped packages.
uuid can be a module (entiergo.org/uuid)
or an org (entiergo.org/uuid/…), never both.
Companies & teams
Org-scoped
One namespace, many modules, one public shelf.
go get entiergo.org/acme/logger
go get entiergo.org/acme/logger/v2
Import paths are forever. Subpackages do not need
their own registry row — only module roots do. They can be listed on
a module for catalog search. Major v2+ is a new module path
(entiergo.org/acme/logger/v2). We do not rename published
paths; publish a new one instead.
Why maintainers publish here
GitHub is a forge. pkg.go.dev is docs. Neither is a Go module
marketplace. These are the reasons a short
entiergo.org/… path should beat GitHub-only.
-
Funding & sponsors
Module pages surface GitHub Sponsors, Open Collective, or custom links with usage context — imported by N modules, company adopters. Sponsors find maintainers from the package, not by digging through a README.
-
Discoverability
A curated catalog: search, tags, trending, new, needs-maintainer, related modules. Search on this site is the first slice of that catalog.
-
Prestige short paths
entiergo.org/sonic-style names feel likego.uber.orgor gonum — brand signal for consumers and a portfolio signal for authors. First-come claims create urgency. -
Maintainer analytics
Downloads over time, importer growth, version adoption, and proxy hints packaged for authors — not buried in third-party dashboards.
-
Trust & quality signals
Health beyond pkg.go.dev defaults: reproducible builds, govulncheck, license clarity, actively maintained, verified publisher. Companies prefer importing trusted brand paths.
-
Zero-friction publish
One flow: claim, push, tag, then a live vanity path, a catalog listing, and a sponsor block. Less ceremony than running your own vanity domain.
-
An audience that buys Go
Homepage, newsletters, module of the week, hiring and partner slots aimed at Go teams — attention a random GitHub repo cannot easily buy.
-
Org storefronts
entiergo.org/acme/…as a public SDK shelf for companies and indie brands: one profile for every module, plus sponsorship.
We own the brand path. Go owns distribution.
We build vanity HTTP, claims, catalog, and publish-to-GitHub. We reuse the public proxy, sumdb, pkg.go.dev, and GitHub. We do not replace them.
- Source
- github.com/entiergo
- Download
- proxy.golang.org
- Integrity
- sum.golang.org
- Docs
- pkg.go.dev
What this is not
Three promises we will not lead with, because they are not true and not the product.
- Not a pkg.go.dev replacement. We feed it. Browsers still land on docs there. pkg.go.dev is an index, not a module proxy.
-
Not faster downloads.
proxy.golang.orgalready does that. We do not host module zip content on the public path. - Not vanity meta alone. Anyone can put nginx in front of GitHub. The storefront — discovery, trust, funding — is the reason to publish here.
Claim a path. Ship under entiergo.org.
Short names are scarce. Register a module or an org namespace,
publish to GitHub, and let go get entiergo.org/… do the
rest.
$