sandworm-guard-js VS fetch-intercept

When building Sandworm’s open-source security & license compliance audits for JavaScript packages, we wanted to generate a catalog of beautiful report visualizations for every library in the npm registry. That is, for every version of every library in the registry. We soon found out — that’s more than 30 million package versions. Good luck generating, uploading, and keeping that amount of HTML pages up to date in a decent amount of time, right?

No whitepaper yet, but here's where the magic happens: https://github.com/sandworm-hq/sandworm-guard-js/blob/main/src/patch.js

You can use https://sandworm.dev to quickly inspect individual licenses for packages when considering adding them as a dependency (note: I'm one of the developers).

Hey all - we’re a small team of developers working on making Javascript more secure! We’re working on a OSS product named Sandworm.JS - a sandboxing & malware detection tool for npm packages. Would love to hear your feedback and feel free to try it out and contribute if you’re passionate about this topic: https://github.com/sandworm-hq/sandworm-js

I'm working on my first react/redux app and I'm not sure where I should call sessionStorage.setItem(). I'm currently storing user credentials from a loginUserSuccess() action but I'm not sure this is where I should be doing that. Furthermore, I'm using fetch to make requests and would like to add the user's authToken to all requests. I was looking into fetch-intercept but not much documentation is provided for modifying headers.