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

[Snyk] Upgrade core-js-compat from 3.37.1 to 3.38.0 #1

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

Conversation

Vin757
Copy link
Owner

@Vin757 Vin757 commented Aug 26, 2024

snyk-top-banner

Snyk has created this PR to upgrade core-js-compat from 3.37.1 to 3.38.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: core-js-compat from core-js-compat GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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

For more information:

Snyk has created this PR to upgrade core-js-compat from 3.37.1 to 3.38.0.

See this package in npm:
core-js-compat

See this project in Snyk:
https://app.snyk.io/org/vin757/project/819dc844-b8bd-4f3b-bdd7-37359d8702a0?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

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

Package New capabilities Transitives Size Publisher
npm/@eslint-community/eslint-plugin-eslint-comments@4.3.0 None +2 98.2 kB eslint-community-bot
npm/@eslint/compat@1.1.0 None 0 45.7 kB eslintbot
npm/@stylistic/eslint-plugin-js@2.2.2 None +3 660 kB eslint-stylistic-bot
npm/confusing-browser-globals@1.0.11 None 0 3.87 kB iansu
npm/eslint-plugin-array-func@5.0.1 None 0 32.3 kB freaktechnik
npm/eslint-plugin-canonical@4.18.1 environment, filesystem Transitive: unsafe +90 17.1 MB gajus
npm/eslint-plugin-es-x@7.7.0 Transitive: filesystem +4 1.3 MB eslint-community-bot
npm/eslint-plugin-import-x@0.5.1 Transitive: environment, filesystem, unsafe +22 3.78 MB jounqin
npm/eslint-plugin-jsonc@2.16.0 environment, filesystem +5 1.61 MB ota-meshi
npm/eslint-plugin-n@17.9.0 filesystem Transitive: unsafe +4 1000 kB weiran.zsd
npm/eslint-plugin-promise@6.2.0 None 0 69.6 kB eslint-community-bot
npm/eslint-plugin-qunit@8.1.1 None +2 561 kB bmishkin
npm/eslint-plugin-redos@4.5.0-beta.6 filesystem 0 14.8 kB makenowjust
npm/eslint-plugin-regexp@2.6.0 None +5 2.28 MB ota-meshi
npm/eslint-plugin-sonarjs@1.0.3 None 0 227 kB sonartech
npm/eslint-plugin-unicorn@54.0.0 Transitive: environment, filesystem, unsafe +19 4.47 MB sindresorhus
npm/eslint@9.5.0 environment Transitive: filesystem, unsafe +33 7.14 MB eslintbot
npm/globals@15.6.0 None 0 170 kB sindresorhus

🚮 Removed packages: npm/@babel/plugin-proposal-duplicate-named-capturing-groups-regex@7.24.7), npm/@babel/plugin-transform-arrow-functions@7.24.7), npm/@babel/plugin-transform-block-scoped-functions@7.24.7), npm/@babel/plugin-transform-block-scoping@7.24.7), npm/@babel/plugin-transform-class-properties@7.24.7), npm/@babel/plugin-transform-class-static-block@7.24.7), npm/@babel/plugin-transform-classes@7.24.7), npm/@babel/plugin-transform-computed-properties@7.24.7), npm/@babel/plugin-transform-destructuring@7.24.7), npm/@babel/plugin-transform-exponentiation-operator@7.24.7), npm/@babel/plugin-transform-for-of@7.24.7), npm/@babel/plugin-transform-literals@7.24.7), npm/@babel/plugin-transform-logical-assignment-operators@7.24.7), npm/@babel/plugin-transform-member-expression-literals@7.24.7), npm/@babel/plugin-transform-modules-commonjs@7.24.7), npm/@babel/plugin-transform-new-target@7.24.7), npm/@babel/plugin-transform-nullish-coalescing-operator@7.24.7), npm/@babel/plugin-transform-numeric-separator@7.24.7), npm/@babel/plugin-transform-object-rest-spread@7.24.7), npm/@babel/plugin-transform-object-super@7.24.7), npm/@babel/plugin-transform-optional-catch-binding@7.24.7), npm/@babel/plugin-transform-optional-chaining@7.24.7), npm/@babel/plugin-transform-parameters@7.24.7), npm/@babel/plugin-transform-private-methods@7.24.7), npm/@babel/plugin-transform-private-property-in-object@7.24.7), npm/@babel/plugin-transform-property-literals@7.24.7), npm/@babel/plugin-transform-reserved-words@7.24.7), npm/@babel/plugin-transform-shorthand-properties@7.24.7), npm/@babel/plugin-transform-spread@7.24.7), npm/@babel/plugin-transform-template-literals@7.24.7), npm/@babel/plugin-transform-unicode-regex@7.24.7)

View full report↗︎

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 NoteCI
Install scripts npm/core-js-pure@3.37.1
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/core-js-pure@3.37.1

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.

2 participants