|author||Filippo Valsorda <firstname.lastname@example.org>||Wed Nov 17 16:25:38 2021 -0500|
|committer||Filippo Valsorda <email@example.com>||Wed Mar 30 20:52:26 2022 +0000|
sumdb/note: catch a Verifiers that returns the wrong Verifier The Verifier method gets the name and hash of the signature, and is supposed to only return a Verifier for that name and hash. If it doesn't, we can catch it by double checking the KeyHash and Name method return values against the signature. Change-Id: I39b2e3616ac389718ebc7eaa6263a43b9152b2fa Reviewed-on: https://go-review.googlesource.com/c/mod/+/364854 Trust: Filippo Valsorda <firstname.lastname@example.org> Run-TryBot: Filippo Valsorda <email@example.com> TryBot-Result: Gopher Robot <firstname.lastname@example.org> Reviewed-by: Al Cutter <email@example.com> Reviewed-by: Russ Cox <firstname.lastname@example.org>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.