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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Security upgrade gulp from 3.9.1 to 5.0.0 #700

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade gulp from 3.9.1 to 5.0.0 #700

wants to merge 1 commit into from

Conversation

adamlaska
Copy link
Owner

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:
    • standalone-packages/monaco-editor/release/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 631/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.2		 Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116		 Yes Proof of Concept

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

Commit messages
Package name: gulp The new version differs by 250 commits.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@snyk-bot
fix: standalone-packages/monaco-editor/release/package.json to reduce…
ee61c33 
… vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116
@google-cla Google CLA
Copy link

google-cla bot commented Mar 29, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@socket-security Socket Security
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/acorn@5.7.1 None 0 564 kB marijn
npm/align-text@0.1.4 None +1 13.5 kB shinnn
npm/clean-css@4.1.11 environment, filesystem, network 0 425 kB jakub.pawlowicz
npm/clean-css@4.2.4 environment, filesystem, network 0 438 kB jakub.pawlowicz
npm/cssom@0.3.4 None 0 58.2 kB nv
npm/expand-tilde@2.0.2 Transitive: environment, filesystem +2 19.7 kB doowb
npm/gulp-typedoc@2.2.0 None +1 37.9 kB rogierschouten
npm/gulp@3.9.1 Transitive: environment, filesystem, network, shell, unsafe +106 2.36 MB phated
npm/gulp@5.0.0 Transitive: environment, filesystem, shell, unsafe +114 3.12 MB phated
npm/http-server@0.11.1 filesystem, network Transitive: environment, shell +12 1.14 MB bigbluehat
npm/lodash@4.17.10 None 0 1.4 MB jdalton
npm/monaco-css@2.1.1 None 0 2.62 MB aeschli
npm/monaco-css@2.2.0 None 0 2.95 MB alexandrudima
npm/monaco-editor-core@0.14.6 None 0 30.8 MB alexandrudima
npm/monaco-html@2.1.1 None 0 1.02 MB aeschli
npm/monaco-html@2.2.0 None 0 1.1 MB alexandrudima
npm/monaco-json@2.1.1 None 0 882 kB aeschli
npm/monaco-json@2.2.0 None 0 975 kB alexandrudima
npm/monaco-languages@1.3.1 None 0 1.1 MB rebornix
npm/monaco-typescript@3.1.0 None 0 19.1 MB alexandrudima
npm/once@1.3.3 None 0 2.77 kB isaacs
npm/optimist@0.6.1 environment +2 106 kB substack
npm/request@2.87.0 environment, filesystem, network +5 645 kB simov
npm/resolve-dir@1.0.1 Transitive: environment, filesystem +7 63.8 kB phated
npm/resolve@1.8.1 filesystem +1 91 kB ljharb
npm/rimraf@2.6.2 filesystem 0 15.1 kB isaacs
npm/source-map@0.5.7 None 0 766 kB tromey
npm/split-string@3.1.0 None 0 13.8 kB jonschlinkert
npm/to-regex@3.0.2 None +3 47.1 kB jonschlinkert
npm/tough-cookie@2.4.3 network +1 610 kB jstash
npm/typedoc@0.11.1 filesystem Transitive: environment, eval +34 45 MB aciccarello
npm/uncss@0.16.2 filesystem Transitive: environment, eval, network, shell, unsafe +49 5 MB mikelambert
npm/vinyl@3.0.0 unsafe +7 126 kB phated
npm/whatwg-encoding@1.0.3 None +1 348 kB domenic
npm/whatwg-mimetype@2.1.0 None 0 16.3 kB domenic
npm/whatwg-url@6.5.0 None +4 527 kB domenic

🚮 Removed packages: npm/bootstrap-vue-helper-json@1.1.1, npm/ccount@1.0.4, npm/chalk@4.1.0, npm/codecov@3.7.2, npm/collapse-white-space@1.0.5, npm/commander@2.19.0, npm/core-js@3.6.5, npm/cross-spawn@7.0.3, npm/debug@4.1.1, npm/decamelize-keys@1.1.0, npm/define-properties@1.1.3, npm/element-helper-json@2.0.6, npm/error-ex@1.3.2, npm/es-abstract@1.17.6, npm/eslint-plugin-vue@7.0.0-beta.3, npm/eslint-scope@5.1.0, npm/eslint-utils@2.1.0, npm/eslint-visitor-keys@1.3.0, npm/eslint@7.9.0, npm/esquery@1.3.1, npm/find-up@2.1.0, npm/fsevents@2.1.3, npm/glob-parent@5.1.1, npm/glob@7.1.6, npm/graceful-fs@4.1.15, npm/gridsome-helper-json@1.0.3, npm/has-symbols@1.0.1, npm/has@1.0.3, npm/hast-util-has-property@1.0.3, npm/hast-util-is-element@1.0.3, npm/is-callable@1.2.0, npm/is-decimal@1.0.3, npm/is-glob@4.0.1, npm/is-hidden@1.1.2, npm/is-regex@1.1.0, npm/is-string@1.0.5, npm/istanbul-lib-coverage@3.0.0, npm/js-beautify@1.13.0, npm/js-yaml@3.13.1, npm/json5@2.1.3, npm/levn@0.4.1, npm/lodash.assign@4.2.0, npm/lodash@4.17.20, npm/lowercase-keys@1.0.1, npm/lru-cache@4.1.5, npm/make-dir@3.1.0, npm/mimic-response@1.0.1, npm/minimist@1.2.5, npm/mkdirp@1.0.4, npm/mocha@8.1.3, npm/ms@2.1.2, npm/node-fetch@2.6.0, npm/normalize-package-data@2.5.0, npm/nuxt-helper-json@1.0.0, npm/nyc@15.1.0, npm/object-keys@1.1.1, npm/object.assign@4.1.0, npm/parse-gitignore@1.0.1, npm/picomatch@2.2.1, npm/prettier-eslint@11.0.0, npm/prettier-tslint@0.4.2, npm/prettier@2.1.2, npm/rc@1.2.8, npm/read-pkg-up@7.0.1, npm/readdirp@3.4.0, npm/resolve@1.17.0

View full report↗︎

@socket-security Socket Security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSource
Potential typo squat npm/monaco-html@2.2.0
Potential typo squat npm/monaco-html@2.1.1

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/monaco-html@2.2.0
  • @SocketSecurity ignore npm/monaco-html@2.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
do-not-merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@adamlaska @snyk-bot