-
Notifications
You must be signed in to change notification settings - Fork 145
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
Build our own list of JS libs #384
Comments
tofumatt
added a commit
that referenced
this issue
Dec 4, 2015
Part of #66, this checks all JS files against a hash of known JS libraries. We're borrowing the current list from the old [amo-validator](https://github.com/mozilla/amo-validator/blob/master/validator/testcases/hashes.txt) but in the future (#384) we'll have our own list. Named filehasher and avoiding the name whitelist because of @andymckay's [thoughtful blog post](http://mckay.pub/2015-01-07-allowed/).
tofumatt
added a commit
that referenced
this issue
Dec 4, 2015
Part of #66, this checks all JS files against a hash of known JS libraries. We're borrowing the current list from the old [amo-validator](https://github.com/mozilla/amo-validator/blob/master/validator/testcases/hashes.txt) but in the future (#384) we'll have our own list. Named filehasher and avoiding the name whitelist because of @andymckay's [thoughtful blog post](http://mckay.pub/2015-01-07-allowed/).
In progress at https://github.com/mozilla/dispensary |
Complete. |
We had a version on NPM at mozilla/dispensary@c98fb2b |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should have a node way of building the JS lib hashes.
@muffinresearch and I talked about this and the whitelist might make sense as a separate repo we could:
The text was updated successfully, but these errors were encountered: