Skip to content
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

Locks event-stream to 3.3.4 #34

Merged
merged 1 commit into from
Nov 26, 2018
Merged

Conversation

joelgallant
Copy link
Contributor

There is an ongoing issue with event-stream since a malicious person took over, see here.

Either way, this locks to a known good version.

package.json Show resolved Hide resolved
@indexzero
Copy link
Owner

Thanks. Getting ramped up on this. Should have a fix out soon.

@FrozenPandaz
Copy link

Thank you for the urgent fix!

ciyer pushed a commit to SwissDataScienceCenter/renku-ui that referenced this pull request Nov 27, 2018
We use npm-run-all to build css before running the app in development mode. The version we were using depends, through ps-tree, on the event-stream package which has been compromised.

- indexzero/ps-tree#34
- dominictarr/event-stream#116
- dominictarr/event-stream#115

Upgrading to the latest npm-run-all fixes this issue.
ableuler pushed a commit to SwissDataScienceCenter/renku-ui that referenced this pull request Nov 27, 2018
We use npm-run-all to build css before running the app in development mode. The version we were using depends, through ps-tree, on the event-stream package which has been compromised.

- indexzero/ps-tree#34
- dominictarr/event-stream#116
- dominictarr/event-stream#115

Upgrading to the latest npm-run-all fixes this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants