You could sign packages and record their signatures along with the version. Which, coincidentally, is basically what https://teapot.nz https://teapot.nz does, e

You could sign packages and record their signatures along with the version. Which, coincidentally, is basically what https://teapot.nz https://teapot.nz does, e.g.: https://github.com/kurocha/geometry/blob/master/development-lock.yml https://github.com/kurocha/geometry/blob/master/development-... Although, I've never considered this in the case of an actual attack. It would make sense to actually fingerprint the entire source tree and record this too somewhere, so when you build it you know you are getting the right thing. Teapot basically defers this to git.