[GH-ISSUE #528] Module path should be canonical #318

New issue

Closed

opened 2026-02-25 22:33:05 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:33:05 +03:00

Owner

Originally created by @jmooring on GitHub (Jun 2, 2023).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/528

See https://go.dev/ref/mod#module-path.

Current:

module filippo.io/mkcert

Should be:

module github.com/FiloSottile/mkcert

Why?

$ go install github.com/FiloSottile/mkcert@latest
go: github.com/FiloSottile/mkcert@latest: github.com/FiloSottile/mkcert@v1.4.4: parsing go.mod:
	module declares its path as: filippo.io/mkcert
	        but was required as: github.com/FiloSottile/mkcert

Yes, I know I can install with go install filippo.io/mkcert@latest, but that was not what I expected based on my experience installing other Go programs.

Originally created by @jmooring on GitHub (Jun 2, 2023). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/528 See <https://go.dev/ref/mod#module-path>. Current: ```text module filippo.io/mkcert ``` Should be: ```text module github.com/FiloSottile/mkcert ``` Why? ```text $ go install github.com/FiloSottile/mkcert@latest go: github.com/FiloSottile/mkcert@latest: github.com/FiloSottile/mkcert@v1.4.4: parsing go.mod: module declares its path as: filippo.io/mkcert but was required as: github.com/FiloSottile/mkcert ``` Yes, I know I can install with `go install filippo.io/mkcert@latest`, but that was not what I expected based on my experience installing other Go programs.

kerem closed this issue

2026-02-25 22:33:05 +03:00

kerem commented

2026-02-25 22:33:06 +03:00

Author

Owner

@bep commented on GitHub (Jun 5, 2023):

The big upside with "vanity paths" like filippo.io/mkcert is that they are host agnostic (which is a great thing if you move your stuff from GitHub to GitLab or something) -- which in some sense makes them ... more canonical?

@bep commented on GitHub (Jun 5, 2023): The big upside with "vanity paths" like `filippo.io/mkcert` is that they are host agnostic (which is a great thing if you move your stuff from GitHub to GitLab or something) -- which in some sense makes them ... more canonical?

kerem commented

2026-02-25 22:33:06 +03:00

Author

Owner

@jmooring commented on GitHub (Jun 5, 2023):

I suppose this is really just a documentation issue, because you don't know the "more canonical" (vanity) import path until you've tried the "less canonical" import path.

@jmooring commented on GitHub (Jun 5, 2023): I suppose this is really just a documentation issue, because you don't know the "more canonical" (vanity) import path until you've tried the "less canonical" import path.

kerem referenced this issue

2026-02-25 22:33:31 +03:00

[PR #344] [CLOSED] if SANs are not present in CSR, use CN #449