-
Notifications
You must be signed in to change notification settings - Fork 42
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: dependencies security review #1828
Comments
ping @chair28980 for help with parenting this issue |
@weboko do you think this work can be included in one of the Milestones defined on the 2024 roadmap? Perhaps |
To me it seems a bit different to what the Milestone is about. Perhaps we can create a new one that would cover compliance with privacy guarantees. cc @fryorcraken |
Reliability needs to come first, then scaling, then privacy. I see this work part of release, maintenance etc. I would not invest too much time on it for now, beyond ensuring |
This is a support request
Problem
js-waku
is client side set of libraries that highly depends on many packages fromnpm
ecosystem.One of our goals is to provide best privacy guarantees possible in web environment. One part of it is addressed by architecture of the network but we shouldn't forget that bad code can get in and cause leaks such as spy on any input on a web page or xss scripting etc
Proposed Solutions
We should not spend too much time on it at least now and lay basement for future improvements.
This should include:
npm audit
at the very least to check leftover dependencies;npm ci
so that it installs locked version of packages;npm audit
not succeeds (or some other requirement that prevents from releasing bad dependencies);Notes
Useful links:
The text was updated successfully, but these errors were encountered: