-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
🔒 feat: Improve security of CI by not running scripts #8626
Conversation
WalkthroughWalkthroughThe overall change involves standardizing the dependency installation process across various configurations and Dockerfiles to a specific Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ? TipsChat with CodeRabbit Bot (
|
10febbe
to
35cb5a8
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #8626 +/- ##
===========================================
- Coverage 34.61% 34.57% -0.05%
===========================================
Files 167 167
Lines 7162 7162
Branches 1212 1212
===========================================
- Hits 2479 2476 -3
- Misses 4532 4537 +5
+ Partials 151 149 -2
Flags with carried forward coverage won't be shown. Click here to find out more. |
NPM packages can run arbitrary scripts when installed. To improve security in CI pass in --ignore-scripts flags.
Developers locally can also choose to use
npm install:ci
if they want the same assurances locally too.Nx requires a post install script to run so we explicitly run it via running
pnpm rebuild nx
. If any other packages require a postinstall scripts we should do the same. This makes it so we never are accidentally introducing a new script we didn't realize is running.