Repository navigation
TRACKING: third party licensing #3884
Description
Some of our direct and indirect dependencies are not using licenses that are approved by Google, so we need to do something about it. We have three options for each of those: ask authors to relicense, reimplement ourselves, or stop using the dependency.
Here's a (maybe incomplete) list:
-
uc.micro- WTFPL (frommarkdown-it). markdown-it might have replacements that are available, so I'll look for those. -
sourcemap-istanbul-instrumenter-loader- WTFPL. We should probably contact the author for this one. Might not be needed. -
jsonify- Public Domain (not a valid license, fromember-cli-preprocess-registry/broccoli-clean-css/json-stable-stringify). We don't need the preprocess-registry and will probably get rid of it.
Other point to consider this completed:
- make a test to check licenses from package.json of every dependencies on Travis.
We might need to make separate issues to track some of those individually.
Activity
hansl commentedon Jan 6, 2017
Shoutout to Robert Spier who found those!
JohannesRudolph commentedon Jan 9, 2017
Alternative reading: Google's legal team should work on approving the WTFPL :-)
filipesilva commentedon Feb 3, 2017
sourcemap-istanbul-instrumenter-loaderis the only one missing now.There seems to be a
yarntool to list licences, we should add a test that uses it.filipesilva commentedon Feb 9, 2017
The
sourcemap-istanbul-instrumenter-loaderauthor at webpack-contrib/istanbul-instrumenter-loader#39 seems to be ok with changing to MIT.build(@angular/cli): update sourcemap-istanbul-instrumenter-loader
build(@angular/cli): update sourcemap-istanbul-instrumenter-loader
build(@angular/cli): update sourcemap-istanbul-instrumenter-loader
build(@angular/cli): update sourcemap-istanbul-instrumenter-loader
build(@angular/cli): update sourcemap-istanbul-instrumenter-loader (#…
filipesilva commentedon Feb 17, 2017
Closed via #4561
build(@angular/cli): update sourcemap-istanbul-instrumenter-loader (a…
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.