x/pkgsite: There doesn't appear to be a way to report packages that no longer exist #43297
What is the URL of the page with the issue?
What is your user agent?
What did you do?
Click the link to the package on GitHub
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
Deleting the module's repo doesn't remove it from the proxy, and pkg.go.dev gets its information from the proxy:
That's by design. It prevents "left pad" situations where someone deletes a module that many others depend on. It also fits with the module design, which decouples module zip files from source code repositories. You can provide a module to the Go ecosystem without a publicly visible source host, just by hosting the module zip file.
That said, there are still some actions that could be taken:
Thanks for the explanation, I was not aware that the Go proxy was used at all times, and this proxy behaviour does sound like a good idea as you described it.
Checking links might not be a good idea at serving time, but I assume the proxy itself is doing some periodic checks for new versions. It might make sense to somehow hook into those checks and eventually disable the pages for packages that have disappeared for an extended period?
Ultimately I don't care enough to push here for some change, but I do think there should be a process to automatically groom out abandoned packages from the live documentation to keep the documentation relevant.
The problem is, it's hard to know something's abandoned unless the author specifically tells us to remove it. Even removal of the source repo might not be enough of a signal—maybe the author decided to deliver the zip directly.
I think a better way to tackle this problem is to clearly indicate certain package properties, and perhaps de-emphasize them in search, without removing the docs completely.
How did you happen to come across this package? That would give us useful information about how we could make it less likely.
I simply wanted to see how others had already integrated the
Some digging led me to an alternative, more recent fork, which is also in
I also expect it depends on Google search voodoo more than anything else.