Skip to content
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

Add vendoring for 3rd party libraries #4

Open
AlexAxthelm opened this issue Feb 15, 2024 · 0 comments
Open

Add vendoring for 3rd party libraries #4

AlexAxthelm opened this issue Feb 15, 2024 · 0 comments

Comments

@AlexAxthelm
Copy link
Contributor

from @bcspragu (via email) who suggests...

moving third-party libraries to a vendored directory. The risk I'd like to mitigate is that one of those deps can change out from under you, and then it can make (authenticated) requests to our backend to exfiltrate data. There's a few possible solutions:

The first approach takes about 15 seconds (adding "integrity=..." to script tags), but I prefer the second (which probably takes a few minutes) because then we can turn on a Content-Security-Policy that blocks all third-party connections, which is a much stronger invariant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant