4 ms·
The way I see it, the root of the problem is that there isn't an independently verifiable association between a package and code commit hash that it's been gene
by sudhirj 7y ago
The way I see it, the root of the problem is that there isn't an independently verifiable association between a package and code commit hash that it's been generated from. My GitHub page can have good code, but no one has any idea what's in the corresponding package.
Does the upcoming builtin package manager on GitHub solve this problem? Does it guarantee that packages are only built from code pushed to GitHub and that associate the commit hash in the metadata in some way?