<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Private Modules on GoMod Vanity URLs</title><link>https://gomodvanityurls.com/tags/private-modules/</link><description>Recent content in Private Modules on GoMod Vanity URLs</description><image><title>GoMod Vanity URLs</title><url>https://gomodvanityurls.com/images/og-default.png</url><link>https://gomodvanityurls.com/images/og-default.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gomodvanityurls.com/tags/private-modules/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Your Go Private Modules Shouldn't Use Raw GitHub Paths</title><link>https://gomodvanityurls.com/blog/why-not-github-import-path/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://gomodvanityurls.com/blog/why-not-github-import-path/</guid><description>From vendor lock-in to IP exposure, using raw GitHub/GitLab paths for Go private module imports has four hidden risks. Vanity URLs are the standard solution recommended by the Go team.</description></item></channel></rss>