Marak/colors.js
View on GitHub ↗ ★ 5,158 JavaScript
get colors in your node.js console
21 mentions on Hacker News by 17 people: 9 stories, 12 comments · first 2010-06-11 · latest 2022-11-22
20082026
-
…release causing issues downstream. Nobody is perfect. Everyone makes mistakes from time to time. https://github.com/Marak/colors.js/commits/master shows 4 commits and 2 releases. Does not seem like a simple mistake > As per our internal…
comment by theamk · 2022-11-22 · in Marak: The reports of my death have been greatly exaggerated -
The commit that caused this: https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d1...
comment by soheilpro · 2022-02-14 · in CVE-2021-23567 -
…Money where mouth is time, do you even have a single commit to a project in either language? [1] https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d1...
comment by brigandish · 2022-01-12 · in An Ode to Ruby -
> https://github.com/Marak/colors.js/blob/5152d16f22789d66e107... So can you point me to where this license says you cannot modify this code? Or that by accepting distribution of one version of this code, you are obligated to distribute…
comment by Macha · 2022-01-11 · in What NPM should do to stop a new colors attack -
…garbage. It's an unquestionably harmful change. Also, you know how you prevent non-commercial use? https://github.com/Marak/colors.js/blob/master/LICENSE - I don't get it, Marak is clearly having some sort of episode*, and people are…
comment by BoorishBears · 2022-01-11 · in What NPM should do to stop a new colors attack -
…more of colors.js (by lines of code) than marak actually got npm to nuke the offending releases: https://github.com/Marak/colors.js/issues/317 right now they are reviewing a request to change the npm target to his repo
comment by fault1 · 2022-01-11 · in What NPM should do to stop a new colors attack -
…to color, and some dude actually had more lines of code edited than the original maintainer: https://github.com/Marak/colors.js/commits/master and faker.js seems to be more or less a port of a ruby library which was a port of a perl…
comment by fault1 · 2022-01-11 · in What NPM should do to stop a new colors attack -
…and there was no CLA involved. github user "DABH" actually had more lines of code than marak did: https://github.com/Marak/colors.js/graphs/contributors npm and github both have terms of service that you agree to when you choose to…
comment by fault1 · 2022-01-11 · in What NPM should do to stop a new colors attack -
…licenses may give others, or npm itself, the right to share Your Content with npm Services again.* https://github.com/Marak/colors.js/blob/master/LICENSE - Seriously, why are people so adamant about defending this? We're all part of a…
comment by BoorishBears · 2022-01-11 · in What NPM should do to stop a new colors attack -
…The accurate description you didn't give is sabotage because he introduced an infinite loop: https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d1...
comment by acdha · 2022-01-10 · in What NPM should do to stop a new colors attack -
Which of the 3 claims are you referring to? The commit is here as far as i know, not deleted: https://github.com/Marak/colors.js/commit/074a0f8ed0c31c35d1...
comment by fulafel · 2022-01-10 · in What NPM should do to stop a new colors attack -
So it looks like the developer's doing this as some sort of meme[0]. Personally I think we should be auditing our packages' dependency chains to ensure they're not reliant upon this developer. [0]: https://web.archive.org/web/20220109232136…
comment by tentacleuno · 2022-01-09 · in Dev corrupts NPM libs 'colors' and 'faker', breaking thousands of apps