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

Update js-yaml to a non vulnerable version #238

Merged
merged 1 commit into from
Apr 9, 2019

Conversation

ceastman-ibm
Copy link
Contributor

snyk test [email protected]

Testing [email protected]...

✗ High severity vulnerability found in js-yaml
Description: Arbitrary Code Execution
Info: https://snyk.io/vuln/SNYK-JS-JSYAML-174129
Introduced through: [email protected]
From: [email protected]
Remediation:
Upgrade direct dependency [email protected] to [email protected] (triggers upgrades to [email protected])

Organisation: ibm-cloud-console
Package manager: npm
Open source: yes
Project path: [email protected]

Tested [email protected] for known vulnerabilities, found 1 vulnerability, 1 vulnerable path.

snyk test [email protected]

Testing [email protected]...

✗ High severity vulnerability found in js-yaml
  Description: Arbitrary Code Execution
  Info: https://snyk.io/vuln/SNYK-JS-JSYAML-174129
  Introduced through: [email protected]
  From: [email protected]
  Remediation: 
    Upgrade direct dependency [email protected] to [email protected] (triggers upgrades to [email protected])




Organisation:      ibm-cloud-console
Package manager:   npm
Open source:       yes
Project path:      [email protected]

Tested [email protected] for known vulnerabilities, found 1 vulnerability, 1 vulnerable path.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.056% when pulling 67ee4c2 on ceastman-ibm:patch-1 into 26e20ac on i18next:master.

@ceastman-ibm
Copy link
Contributor Author

@jamuhl can you review my PR?

@jamuhl jamuhl merged commit ccffd22 into i18next:master Apr 9, 2019
@jamuhl
Copy link
Member

jamuhl commented Apr 9, 2019

thank you for creating the PR: was published in [email protected]

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.

3 participants