-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove event-stream dependency #149
Comments
To know if your project is in danger, run:
The bad actor has publishing rights to Here is an example result from one of my projects:
|
Wow, thank you for the pointing. |
@mysticatea Maybe try replacing the unmaintained ps-tree with something else like https://github.com/sindresorhus/fkill? |
I have removed |
Hmm, maybe it's not wise to have released it as a minor bump if if 4.1.4 is buggy? |
I will try pidtree package and publish fixed version ASAP. |
I have published |
It includes an upgrade to avoid the malicious attack included in dependency of npm-run-all. See: mysticatea/npm-run-all#149
It includes an upgrade to prevent the malicious attack included in dependency of npm-run-all. See: mysticatea/npm-run-all#149
It includes an upgrade to prevent the malicious attack included in dependency of npm-run-all. See: mysticatea/npm-run-all#149
npm-run-all 4.1.3 depends indirectly on flatmap-stream, which has been yanked from npm because it contained malicious code: https://www.npmjs.com/advisories/737 mysticatea/npm-run-all#149
npm-run-all 4.1.3 depends indirectly on flatmap-stream, which has been yanked from npm because it contained malicious code: https://www.npmjs.com/advisories/737 mysticatea/npm-run-all#149
@mysticatea please check dominictarr/event-stream#116
The text was updated successfully, but these errors were encountered: