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 Security Concerns #387

Open
mgifford opened this issue Mar 17, 2021 · 2 comments
Open

Add Security Concerns #387

mgifford opened this issue Mar 17, 2021 · 2 comments

Comments

@mgifford
Copy link

Adding 3rd Party Javascript is always a bit of a security concern. You have to really trust that they are implementing best practices and being incredibly diligent in maintaining it.

I would be surprised if most widget companies are that committed to either privacy or security.

I suspect this isn't the only violation:
https://www.govtech.com/security/Cryptojackers-Hit-Government-Websites-A-New-Flavor-of-Hacking-Courtesy-of-Third-Party-Code.html

I bet there are examples where more than users CPU cycles were being taken.

@karlgroves
Copy link
Owner

@mgifford can you provide some suggested wording for this?

@mgifford
Copy link
Author

mgifford commented May 4, 2021

How about something like this:

Adding 3rd party JavaScript libraries to your page always adds additional security risks, reduces page performance and increases the CO2 produced to load the page. Any additional JavaScript files should be added to your page only after careful considering the alternatives.

I wondered off beyond just security, but think it drives the point home.

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

2 participants