You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think you need to take any immediate action, but I figured I should give you a heads up just in case.
A few days ago a malicious package was added as a dependency to event-stream, which is a dependency to ps-tree, which in turn is a dependency to npm-run-all. This last one is used extensively as part of the build tools on this SDK.
To make sure this does not become a problem, it might be a good idea to update npm-run-all to the recently-published 4.1.5 version (it's currently pinned at 4.1.2 in all the packages/**/package.json files.)
Edit: The current versions used here are at the moment are not affected, but upgrading is still a good idea to make sure they never are. And just to be clear, this would only affect the machines of those developing the SDK and not the end users of the library.
Steps to reproduce:
n/a
Relevant Code:
n/a
The text was updated successfully, but these errors were encountered:
Describe your environment
Describe the problem
I don't think you need to take any immediate action, but I figured I should give you a heads up just in case.
A few days ago a malicious package was added as a dependency to
event-stream
, which is a dependency tops-tree
, which in turn is a dependency tonpm-run-all
. This last one is used extensively as part of the build tools on this SDK.To make sure this does not become a problem, it might be a good idea to update
npm-run-all
to the recently-published 4.1.5 version (it's currently pinned at 4.1.2 in all thepackages/**/package.json
files.)Relevant discussions:
mysticatea/npm-run-all#149
dominictarr/event-stream#116
Edit: The current versions used here are at the moment are not affected, but upgrading is still a good idea to make sure they never are. And just to be clear, this would only affect the machines of those developing the SDK and not the end users of the library.
Steps to reproduce:
n/a
Relevant Code:
n/a
The text was updated successfully, but these errors were encountered: