What NPM should do to stop a new colors attack

Re:What NPM should do to stop a new colors attack by ratg13 on Tuesday January 11, 2022 @02:07AM (#29888489)

This still leaves the elephant in the room: who decides when this line has been crossed?

[ Parent | on HN ]

Re:What NPM should do to stop a new colors attack by thirtyseven on Tuesday January 11, 2022 @04:12AM (#29889237)

I think the organizations that spend tons of money to run the central repositories we all use are a good candidate for that.

[ Parent | on HN ]

Re:What NPM should do to stop a new colors attack by rakoo on Tuesday January 11, 2022 @07:34AM (#29890765)

I would have said it's the organization that earn tons of money and don't give a cent to developers if they can avoid it who should think about the structure they have created and profited from and now realize open source doesn't exist in abundance like air.

[ Parent | on HN ]

Re:What NPM should do to stop a new colors attack by toxik on Tuesday January 11, 2022 @03:08AM (#29888861)

Intent is what matters, was it meant as an attack - and it kind of was but Joe Developer Schmoe really just got caught in the crossfire of some guy who watched Mr. Robot one time too many.

To answer your question directly, I think the jury’s still out and it will depend on the repercussions. So far it seems to have been a nuisance at worst.

[ Parent | on HN ]