node-ipc
n
node-ipc | n | |
---|---|---|
76 | 50 | |
42 | 18,540 | |
- | - | |
2.3 | 7.0 | |
8 months ago | 20 days ago | |
JavaScript | Shell | |
MIT License | MIT License |
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.
node-ipc
-
gotta admit, gadgetbridge is awesome!
It should be noted that when developers have the ability to upload packages themselves, there is no guarantee that what the user gets corresponds to the source code that is available. The malware in node-ipc is suspiciously absent from the published source repository which has the latest release in 2021. If you were pulling directly from the source code you would not have seen this. This is an issue with npm, not libre software or "open source."
- How far it's fallen. Bring back my dog.
- Any updates on Rust, and node ipc?
- Anonymous Takes Anti-Putin Battle to Russian People with Printer Attack to Disrupt Kremlin's Propaganda
- Embedded Malicious Code in node-ipc
- Commentary on the Node-IPC incident and open source supply chains
-
The authors of node-ipc have pushed malware in an update, which wipes your disk if you happen to have Russian or Belorussian IP address. This affects some large projects like Vue CLI where it is a dependency.
Direct link to the github discussion: https://github.com/RIAEvangelist/node-ipc/issues/233 (many comments have been removed)
-
Sabotage: Code added to popular NPM package wiped files in Russia and Belarus
Actually, to my knowledge, I was the very first person to discover the malware contained in the commit range of 847047cf7f81ab08352038b2204f0e7633449580 -> 6e344066a0464814a27fbd7ca8422f473956a803
-
On the Weaponisation of Open Source
From the article:
> I don’t think this can be classed as open source anymore:
> The definition of an Open Source License is quite clear:
> 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons.
> I don’t really want to have to read through each of my dependencies and transitive dependencies licences to determine whether I am agreeing to discriminatory terms by using a library.
I think the author of the article has misunderstood the definition, thus reached the wrong conclusion.
The non-discrimination rule applies only to accessibility and nothing else. Simply put, you provide the same code/product to everybody, including Satan Claus and Mr Putin under the same set of condition and permissions. Adding/removing malicious code does not change the fact that the code is by definition open sourced.
All and all, this is not a license problem.
Now, talk about node-ipc, which just got attacked by mobs (see https://github.com/RIAEvangelist/node-ipc/issues?q=is%3Aissu...).
If an open source project is a scam, then it's a scamware. If an open source project is malicious, then it's a malware.
Personally, as a normal human being, it is hard to keep a peace of mind after watching how the Russians fired multiple heavy rounds to kill the elderly couple who just traveling peacefully in a car down the road near a hospital. It is even harder to keep a peace of mind after watching a video recorded by a son showing how the Russians shoot and killed his father who sits in the driver's seat right beside him. I fully understand and respect the anger.
However, I do agree that people need to be more mature on this even during this difficult time. Turn your project into a malware only hurts your own reputation and people who trusted you. Once the trust is gone, it might never recover. There are many ways to actually hurt those who contributed the invasion. Be constructive and accurate, or at very least don't be destructive.
- Open Source Maintainer Sabotages Code to Wipe Russian, Belarusian Computers
n
-
Looks like npm is installed but does not work.
use n or nvm to manage installed node/npm versions.
-
Help!
I have node installed, via n
-
How To manage Different Versions of Node in Your system
1 - n is a tool that allows you to easily switch between different versions of Node.js. Follow the official guide in case this does not work for you due to an update or need a command not highlighted below. Here's how you can use n to switch between Node.js versions:
-
Nvm or homebrew for Node install
Listing people's recommendations with links below. I'm glad I asked this question. I received a lot of good recommendations. Thanks All! * nvm (https://nvm.sh) - Simple to use and easy to follow instructions with more in-depth configuration for those that need it. Some experienced a slightly slower terminal. Supports nodjs, iojs, and node version per project/directory. * fnm (https://github.com/Schniz/fnm) - Built with speed in mind. It is like nvm, but faster. Also supports node version per project/directory. * Volta (https://volta.sh/) - Looks easy to use and has good documentation. * asdf (https://asdf-vm.com/) - Supports multiple runtimes and tools by adding plugins. Admittedly, is a bit confusing and more than I need right now (Node, Rust, Python, Ruby, etc.) * Homebrew (https://brew.sh/) - Not a version manager but can act like one by installing nvm, fnm, asdf, or others. Some additional configuration may be needed. * Proto (https://moonrepo.dev/proto) - Supports Bun, Deno, Node.js (npm, pnpm, yarn), Rust, and Go. Also good documentation. Setup looks a bit complex to me :/. * n (https://github.com/tj/n) - Supports Node and npm per project. Simple and to the point.
- Is there nvm for non-technical people?
-
Why are there no virtual environments for front end JS?
And there are virtual environment; kind of. I just actually started using this, but there's n.
-
Manage Node.js Versions With n
Today, let's find out why you would need multiple versions of Node.js in the first place and how to manage them efficiently with n, a Node.js version manager that is very developer-friendly.
-
Flatpaks 🥰
I used n. It was pretty good. I still hated every time I had to change versions and the idea of making dockers for this came with a friend. Thankfully, I don't have that.project anymore
-
Linux: Best way to install node & npm
https://github.com/tj/n to install node and manage versions
-
What do use to manage your nodejs installation?
N package since I found it out. Happy for both local pc and servers.
What are some alternatives?
vue-cli - 🛠️ webpack-based tooling for Vue.js Development
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
es5-ext - ECMAScript extensions (with respect to upcoming ECMAScript features)
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
peacenotwar - Attempts to determine if the computer its running on has an IP originating from Russia or Belarus. If it is then depending on the version of the malware either attempts to delete all files on the computer, or creates a text file on the computers desktop protesting the war in ukraine.
nodenv - Manage multiple NodeJS versions.
Flow.Launcher - :mag: Quick file search & app launcher for Windows with community-made plugins
volta - Volta: JS Toolchains as Code. ⚡
create-vue - 🛠️ The recommended way to start a Vite-powered Vue project
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
node-ipc-dependencies-list - List of all dependencies affected by node-ipc malicious commit
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions