I made it through my hands on learning session: chore: package as nix flake by blaggacao · Pull Request #274 · zegl/kube-score · GitHub on nix flakes. 
However, out of gratefulness to be willing to include nix flakes builds (much more quickly than it would be possible on nixpkgs *), if feel obliged to provide the esteemed and brave package maintainer with an easy to update way for this vendorSha256 thing. Within intermediate time frame, for him, it all boils down to maintaining this vendorSha256 thing!
What can I tell @zegl, if he was actually about to pull this off?
See also: chore: package as nix flake by blaggacao · Pull Request #274 · zegl/kube-score · GitHub
That’s the kind of real (and very focused) use case for goreleaser, etc. support. QED.
* My real other option to seeking relieve in horizontal scaling of package distribution, is to contribute marginally to the already dire overload of nixpkgs maintainers: all nixpkgs maintainer tools optimizations and workflows only ever scale so much so until they don’t any more. Flakes are the solution, they scale with every marginal adopter. And as long as the reproducibility ethics of the nix package manager can be enforced it has the potential of developing a whole different dynamic of its own.