Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Old jasmine version used by protractor #3811

Closed
shumailarshad opened this issue Dec 9, 2016 · 1 comment
Closed

Old jasmine version used by protractor #3811

shumailarshad opened this issue Dec 9, 2016 · 1 comment

Comments

@shumailarshad
Copy link

shumailarshad commented Dec 9, 2016

Bug report

  • Node Version: 4.2.6
  • Protractor Version: 4.0.13
  • Angular Version: na
  • Browser(s): na
  • Operating System and Version na
  • Your protractor configuration file
  • A relevant example test
  • Output from running the test
  • Steps to reproduce the bug
  • The URL you are running your tests against (if relevant)

We have vulnerability check implement in our project which has found vulnerability in minimatch version. Protractor not using latest version of jasmine which will fix this issue.

Name Installed Patched Path More Info
minimatch 0.3.0 >=3.0.2 OURPROJECTNAME@0.0.184 > protractor@4.0.13 > jasmine@2.4.1 > glob@3.2.11 > minimatch@0.3.0 https://nodesecurity.io/advisories/118

@cnishina
Copy link
Member

cnishina commented Dec 9, 2016

This has been considered. We originally upgraded jasmine; however, it also causes issue #3609. We downgraded back to jasmine@2.4.1 and awaiting a new release of jasmine-npm with this change: jasmine/jasmine-npm#98.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants