-
Notifications
You must be signed in to change notification settings - Fork 27
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: lavamoat #712
base: master
Are you sure you want to change the base?
feat: lavamoat #712
Conversation
c39da8d
to
2ada178
Compare
2ada178
to
2306201
Compare
@@ -0,0 +1,1383 @@ | |||
{ |
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.
This file is generated by lavamoat automatically (because we have generatePolicy: true
in our plugin config). All manual changes are done in the policy-override.json
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.
Waiting dependencies review
eec7214
65abf08
to
b3b2e5e
Compare
b3b2e5e
to
73595cf
Compare
73595cf
to
9631ec1
Compare
77db504
to
14de471
Compare
14de471
to
e473bdf
Compare
73ca38e
to
9b966af
Compare
- name: Install ttag-cli globally | ||
run: npm install -g ttag-cli |
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.
question(non-blocking): Why do we need to install it globally?
Motivation
Add LavaMoat to protect against supply chain attacks and upgrade react-scripts to version 5.
Description
Added LavaMoat webpack plugin to production builds only. This required upgrading react-scripts from v4 to v5, which in turn required several changes:
Acceptance Criteria
LavaMoat runs only in production builds as
@lavamoat/webpack
is missing a hookDevelopment builds work without LavaMoat
All functionality remains unchanged with lavamoat and react-scripts v5 activated
Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.