peacenotwar
npm
peacenotwar | npm | |
---|---|---|
33 | 48 | |
155 | 17,233 | |
- | - | |
7.0 | 2.1 | |
over 1 year ago | over 3 years ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 only | Artistic License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
peacenotwar
-
Open Source Hacktivism, Open Source Gains Traction in the Enterprise, and More: Open Source Matters
Today, with an ongoing war between Russia and Ukraine, some open source maintainers have taken it upon themselves to protest the war via changes to their code that express anti-war rhetoric via messages that display when the software is run. However, one maintainer in particular took it to the next level. Brandon Nozaki Miller, published a library on GitHub named peacenotwar that simply printed an anti-war message to the computer it was run on. This package is harmless on its own, but things got interesting when he included this package as a dependency in the node-ipc module he maintains. Users who downloaded the latest version of node-ipc to a machine in Russia would be subject to complete data destruction. Miller defended the act by claiming that this is all documented publicly and that users who don’t want this installed on their machine should lock their dependencies to older versions.
-
node-ipc go brrrr
apparently an NGO working in belarus got affected
-
American NGO using node-ipc lost 30k files detailing war crimes
From that reddit thread, here is the github issue the paste originated from.
https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Human Rights Organization in Ukraine was the victim of a malware attack by an "activist" targeting Russian and Belorusian IPs
the repo where this issue was posted simply created a .txt file on the user's machine, doesn't wipe anything: https://github.com/RIAEvangelist/peacenotwar/issues/45
-
Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
This headline is fucking yikes, the node package that they're talking about is fully open source and does nothing but make a text file in 3 locations. It does nothing remotely close to "wiping" computers, lmfao.
-
BIG sabotage: Famous npm package (node-ipc) deletes files to protest Ukraine war
His actions destroyed over 30,000 messages & files detailing war crimes committed by Russian in Ukraine belonging an American NGO that monitors human rights infringements in eastern Europe. Cool protest, bro.
-
Un paquet npm compromis par l'auteur efface les fichiers sur les ordinateurs russes et biélorusses lors de l'installation, pour protester contre l'invasion de l'Ukraine par la Russie
Première victime collatérale
-
Developers of node-ipc edited the software so that anyone with a russian or belarusian IP would get their drive scrubbed clean of data, drama ensues.
Links to drama: https://github.com/RIAEvangelist/peacenotwar/issues, https://github.com/RIAEvangelist/node-ipc/issues
-
My entire PC got wiped Do not download
The package uses https://github.com/RIAEvangelist/peacenotwar to deliver the message.
But I don't understand why/how it would wipe the PC. Unless I missed something, the code from the package does not delete anything.
> This code serves as a non-destructive example of why controlling your node modules is important. It also serves as a non-violent protest against Russia's aggression that threatens the world right now.
Nah, the author knew it's would be controversial. The first sentence is there as an excuse.
- Node-ipc supply chain attack: peacenotwar
npm
-
XML is better than YAML
The fact that JSON doesn't support comments is so annoying, and I always thought that Douglas Crockford's rationale for this basically made no sense ("They can be misused!" - like, so what, nearly anything can be misused. So without support for comments e.g. in package.json files I have to do even worse hacky workaround bullshit like "__some_field_comment": "this is my comment"). There is of course jsonc and JSON5 but the fact that it's not supported everywhere means 10 years later we still can't write comments in package.json (there is https://github.com/npm/npm/issues/4482 and about a million related issues).
-
Jest not recommended to be used in Node.js due to instanceOf operator issues
Things like the sparkline charts on npmjs (e.g. https://www.npmjs.com/package/npm ) are interactive SVGs. I think they're pretty common for data visualizations of all kinds
-
JavaScript registry NPM vulnerable to 'manifest confusion' abuse
I actually did a POC 7 years ago about this - https://github.com/tanepiper/steal-ur-stuff
It was reported to npm at the time, but they chose to ignore it - https://github.com/npm/npm/issues/17724
-
I'm a Teapot
Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses.
I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM.
Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult
https://github.com/npm/npm/issues/20791
-
Dissecting Npm Malware: Five Packages And Their Evil Install Scripts
I should really get around to how I discovered this 6 years ago and still nothing done about it
-
Attackers are hiding malware in minified packages distributed to NPM
Whenever something like this comes up I usually have to tap the sign (and the original report)
-
NPM Vs PNPM
NPM is not "Node Package Manager". https://www.npmjs.com/package/npm
-
A not so unfortunate sharp edge in Pipenv
> which can be overriden with env setting
Support for this is not great. Lots of packages still don't support this properly. My experience matches the 2015 comment https://github.com/npm/npm/issues/775#issuecomment-71294085
> Not sure why "symlinks" would be involved.
If you make your node_modules a symlink, multiple packages will fail. Even if you're not interested in doing that, others are.
> What NPM does is leaps and bounds ahead
Unless you change your node / gyp version. It doesn't really have a concept of runtime version. You can restrict it, but not have two concurrent versions if they conflict.
-
Front-end Guide
[email protected] was released in May 2017 and it seems to address many of the issues that Yarn aims to solve. Do keep an eye on it!
-
Framework axios pushed a broken update, crippling thousands of websites
I think it's had been supposed to do that since forever. Apart from some bug in npm 5.3. Are you sure your package-lock versions actually conform to the semver ranges in your package.json?
What are some alternatives?
node-ipc - A nodejs module for local and remote Inter Process Communication (IPC), Neural Networking, and able to facilitate machine learning.
pnpm - Fast, disk space efficient package manager
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
corepack - Zero-runtime-dependency package acting as bridge between Node projects and their package managers
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
spm
protestware-list
yarn - The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
Bower - A package manager for the web
tiny-http - Low level HTTP server library in Rust
jspm