[Snyk] Fix for 1 vulnerabilities

[admmasters]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	768/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5	Prototype Pollution SNYK-JS-LODASH-6139239	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: plist

The new version differs by 20 commits.

• c71d9f7 History: add v2.0.1
• de136c8 Release 2.0.1
• 6bcca80 History: add missing commits for v2.0.0 release
• 00fb1c4 Release 2.0.0
• 1fe01b3 History: normalize
• 90deef5 remove deprecated functions
• 18d3be9 Merge pull request [Snyk] Fix for 9 vulnerabilities #68 from mrzmyr/add-verbose-examples
• 7fc9a5b Merge pull request [Snyk] Security upgrade ws from 1.1.5 to 8.17.1 #76 from amilajack/patch-1
• d475cd8 Added travis ci support for node 6
• 0c06929 Merge pull request [Snyk] Fix for 1 vulnerabilities #73 from mitchhentges/reduce-package-size
• 04c8ee7 Update dependencies
• d8d74cb Merge pull request [Snyk] Security upgrade yeoman-environment from 1.5.3 to 2.0.4 #69 from agoldis/master
• 97c02b3 travis: add `sudo: false` and test more node versions
• 3d666f1 Merge commit '6daf4cc34ea26ba5829021878ecec74754beaf85'
• 54c821e [Snyk] Fix for 1 vulnerabilities #71 - fixed and added test
• 6daf4cc Merge pull request [Snyk] Fix for 14 vulnerabilities #70 from chriskinsman/master
• 4afb7c5 Fix Cannot read property 'nodeValue' of undefined exception that is thrown when a <key></key> construct appears in plist
• f360d7d [Snyk] Security upgrade yeoman-environment from 1.5.3 to 4.0.0 #66 - fixed empty keys and added tests
• 421c7f2 [Snyk] Security upgrade yeoman-environment from 1.5.3 to 4.0.0 #66 - fixed empty key
• a88aa4d add verbose examples

See the full diff

Package name: xcode

The new version differs by 29 commits.

• 1cd2208 bumping to 0.9.3
• 3f29dfc Merge branch 'zhuangya-upgrade'
• 6d5c79c Merge branch 'upgrade' of https://github.com/zhuangya/node-xcode into zhuangya-upgrade
• 9592ed1 bumping version to 0.9.2
• bba0d31 chore: upgrade PEG, simple-plist and nodeunit
• 078625f Merge branch 'freiserg-master'
• 31b6d49 Merge branch 'master' of https://github.com/freiserg/node-xcode into freiserg-master
• b735df9 Bumping to 0.9.1
• f51dca9 Merge branch 'AbnerZheng-master'
• 43c0d59 Merge branch 'master' of https://github.com/AbnerZheng/node-xcode into AbnerZheng-master
• ffb938b Update a uuid module
• 1568955 Merge branch 'innovative1-master'
• 96660f2 Tests for knownRegions
• 92b4acd Adding and removing knownRegions to/from PBXProject section
• 59506f1 Merge branch 'kelvinhokk-master'
• 1d30663 Merge branch 'master' of https://github.com/kelvinhokk/node-xcode into kelvinhokk-master
• 7f26cc0 Merge branch 'superserg8-master'
• fb628c6 pbxProject removeTargetAttribute
• c78d781 pbxProject addTargetAttribute
• f40466f change tail recursive -> iterate
• e842a9e added PBXVariantGroup for localization and nodeunit test cases
• 4cca2f6 Merge branch 'sundbry-shell-step'
• cab0d0d Test case for PBXShellScriptBuildPhase
• f7a77f1 Upgrade to 0.9.0

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

[changeset-bot]

⚠️ No Changeset found

Latest commit: dd27eb8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR