3 ms·
I agree that the thirdparty javascript files also should be supplied in full, and minified during the build process. However, I've found the originals so you c
by mindcrash 10y ago
I agree that the thirdparty javascript files also should be supplied in full, and minified during the build process.
However, I've found the originals so you can still check if they contain 'contaminated' code.
chrono: https://www.npmjs.com/package/chrono-node https://www.npmjs.com/package/chrono-node - a natural language date parser for Node and Browserify
notie: https://www.npmjs.com/package/notie https://www.npmjs.com/package/notie - a clean and simple notification, input, and selection suite for javascript, with no dependencies
readability: https://github.com/arrix/node-readability https://github.com/arrix/node-readability - Node implementation of Arc90's Readability (however seems this code has been slightly modified)
semantic: https://github.com/Semantic-Org/Semantic-UI https://github.com/Semantic-Org/Semantic-UI - Semantic UI JS support
stopwords: list of stopwords for the english language
- diggan 10y agoIt serves no purpose, reviewing third-party code that you don't even know is the same that is distributed. But anyways, since Chrome has autoupdate for addons, it doesn't matter if you're reviewing the addons you install or not, because it can change at any point.
- Falcon9 10y agoIf you clone it on your local machine you also won't receive any automatic updates.