-
Notifications
You must be signed in to change notification settings - Fork 300
fix: pin npm commands by hash in build scripts for supply chain security #7081
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: pin npm commands by hash in build scripts for supply chain security #7081
Conversation
mukeshsp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the conflicts and failing tests
louib
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure those scripts are still used? I think those three modules are published with lerna just like all the other BitGoJS modules
modules/bitgo/scripts/publish.sh
Outdated
| # install | ||
| npm install | ||
| # install - generate package-lock.json first, then use npm ci for reproducible builds | ||
| npm install --package-lock-only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't regenerating a package-lock.json file first defeat the purpose of running npm ci? Why would the package-lock.json file be incomplete at the time of publishing?
Marzooqa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI failing
12256c3 to
3f2c274
Compare
TICKET: DX-1510
TICKET: DX-1510
Replace unpinned
npm installwithnpm ciacross publish scripts to prevent supply chain attacks and ensure reproducible builds.