Migrate to DABH's fork of colors #469
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #337
As I understand it, the original maintainer of the
colorspackage, Marak, previously sabotaged it for a laundry list of political/ideological reasons, involving Aaron Schwartz, the Ukraine war, and big corporations using his code. npm removed the malicious version against the old maintainer's will, but one still has to wonder if he might one day sabotage his packages again. Anything by him is kinda suspect, now.Someone else called DABH took over maintainership after the sabotage. Let's point at the npm package he controls, just to be sure that bumping our dev dependencies in future won't install malware.
The (tiny, trivial) example script that uses
colorsstill seems to work after this: