Repository navigation
express@5.3.0 rebuilds byte-for-byte from its provenance commit
#7591
ujjwalv01
started this conversation in
Show and tell
Replies: 1 comment
|
Hii @ujjwalv01 👋 This is a really interesting initiative for improving npm supply chain security! A few things I found particularly valuable:
Overall, releaseproof looks like a useful contribution towards making open-source package releases more transparent and trustworthy. Great work on this! If this answer solves all your doubts, could you please mark my answer as solved? Or, if you still have any doubts, please let me know! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Express maintainers 👋
I maintain releaseproof (https://github.com/ujjwalv01/releaseproof), an open-source tool that verifies an npm release's provenance, rebuilds it from the certified commit in a hardened Docker container, and compares the tarballs file by file.
express@5.3.0 → MATCHES SOURCE: 10/10 files identical to a clean build of cf6722b, provenance verified.
One low-severity note it reported, in case it's useful: the repository has no lockfile, so a rebuild may pick up different dependency versions than the original release build. For express that doesn't affect the published files (they matched), but it's the kind of drift releaseproof flags.
If you'd like a check like this after every release (or before approving a staged release), it's one Action step:
uses: ujjwalv01/releaseproof@v0.2.2. No permissions needed.Thanks for Express!
All reactions