Using /Users/Suguru/browser-laptop/package.jsonįont-awesome-webpack 0.0.4 → 0.0.5-beta.2īabel-plugin-transform-react-constant-elements 6.4.0 → 6.23.0īabel-plugin-transform-react-inline-elements 6.4.0 → 6.22.
It also shows you how many ads and trackers are being blocked by Brave on each website you visit. Security/privacy/tracking code built in & it would never be noticed by the people that use these files.ĭoes anyone here have any technical knowledge about this situation that they would like to share in an effort to improve our (my atleast) understanding of this situation?Īfter removing semver specifications, it would be updated with npm-check-updates like this: Run ncu with -u to upgrade package.jsonīrave-MacBook-Pro:browser-laptop Suguru$ ncu Brave then takes this a step further, allowing you to choose your Shield settings (what is being blocked by Brave) on a per-site or browser-wide basis. These (possibly 100’s or more) files could include Which means that nomatter how many precautions we take in an effort to secure our browsers for privacy (in particular) we are left with a HUGE gaping hole that is a backdoor for anyone who is serious about invading internet user privacy (at the very least).Ī serious threat could be mounted by those with the resources, to create many (100’s of useful) JavaScript files that would be attractive to other JavaScript dev’s to use (or parts of them), as these files would via node.js/npm make the dev’s life so much easier when it comes to producing their finished product. If things are as they look to me to be then there are appalling security vulnerabilities that JavaScript brings via node.js/npm.
0 kommentar(er)
