Skip to content

[Snyk] Upgrade terser from 5.9.0 to 5.30.3 #17

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

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

Conversation

mcgithub01
Copy link
Owner

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


Snyk has created this PR to upgrade terser from 5.9.0 to 5.30.3.

ℹ️ 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 55 versions ahead of your current version.
  • The recommended version was released a month ago, on 2024-04-03.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-TERSER-2806366
479/1000
Why? Has a fix available, CVSS 5.3
No Known Exploit

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

Release notes
Package name: terser
  • 5.30.3 - 2024-04-03

    5.30.3

  • 5.30.2 - 2024-04-02

    5.30.2

  • 5.30.1 - 2024-04-01

    5.30.1

  • 5.30.0 - 2024-03-27

    5.30.0

  • 5.29.2 - 2024-03-14

    5.29.2

  • 5.29.1 - 2024-03-06

    5.29.1

  • 5.29.0 - 2024-03-06

    5.29.0

  • 5.28.1 - 2024-02-23

    5.28.1

  • 5.28.0 - 2024-02-23

    5.28.0

  • 5.27.2 - 2024-02-19

    5.27.2

  • 5.27.1 - 2024-02-15
  • 5.27.0 - 2024-01-17
  • 5.26.0 - 2023-12-07
  • 5.25.0 - 2023-12-04
  • 5.24.0 - 2023-10-31
  • 5.23.0 - 2023-10-30
  • 5.22.0 - 2023-10-16
  • 5.21.0 - 2023-10-03
  • 5.20.0 - 2023-09-20
  • 5.19.4 - 2023-09-04
  • 5.19.3 - 2023-08-29
  • 5.19.2 - 2023-07-21
  • 5.19.1 - 2023-07-17
  • 5.19.0 - 2023-07-11
  • 5.18.2 - 2023-06-27
  • 5.18.1 - 2023-06-19
  • 5.18.0 - 2023-06-12
  • 5.17.7 - 2023-06-01
  • 5.17.6 - 2023-05-23
  • 5.17.5 - 2023-05-22
  • 5.17.4 - 2023-05-16
  • 5.17.3 - 2023-05-09
  • 5.17.2 - 2023-05-08
  • 5.17.1 - 2023-04-18
  • 5.17.0 - 2023-04-18
  • 5.16.9 - 2023-04-10
  • 5.16.8 - 2023-03-24
  • 5.16.6 - 2023-03-09
  • 5.16.5 - 2023-02-23
  • 5.16.4 - 2023-02-17
  • 5.16.3 - 2023-02-03
  • 5.16.2 - 2023-01-30
  • 5.16.1 - 2022-12-02
  • 5.16.0 - 2022-11-24
  • 5.15.1 - 2022-10-05
  • 5.15.0 - 2022-08-23
  • 5.14.2 - 2022-07-13
  • 5.14.1 - 2022-06-10
  • 5.14.0 - 2022-05-30
  • 5.13.1 - 2022-04-29
  • 5.13.0 - 2022-04-26
  • 5.12.1 - 2022-03-14
  • 5.12.0 - 2022-03-01
  • 5.11.0 - 2022-02-21
  • 5.10.0 - 2021-11-15
  • 5.9.0 - 2021-09-21
from terser GitHub release notes
Commit messages
Package name: terser
  • 3621443 5.30.3
  • 9576c0d update changelog
  • 0e04a22 fix precedence of `#private in ...` operator
  • 694846c 5.30.2
  • c03b0e2 update changelog
  • 3f912af avoid optimizations inside computed keys. Closes #1514. Closes #272
  • 1b5cbc2 5.30.1
  • 97539db update changelog
  • a05702d tighten is_identifier_string for typical environments
  • 1306a72 remove useless slash-escapes of non-ascii characters. Closes #1506
  • 1161ff1 fix changelog
  • a0b4e3a 5.30.0
  • 89ca2bb update changelog
  • 0fc03ec improve handling of self-referential classes (#1504)
  • 2b0fb28 5.29.2
  • f2901b6 update changelog
  • 1cdfba8 make sure 'computed_props' creates string keys. Closes #1500
  • 03660f8 take into account the evaluated size when inlining. Closes #1454
  • 6f269e4 5.29.1
  • 2e49394 update changelog
  • dc02fb5 fix optimization of all-bits mask check
  • 7cab6e8 5.29.0
  • 28cf54c update changelog
  • b272e76 Remove needless wrapper for from_moz (#1499)

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Copy link

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

Package New capabilities Transitives Size Publisher
npm/[email protected] environment, eval Transitive: filesystem, shell +10 4.18 MB fabiosantoscode

🚮 Removed packages: npm/[email protected]

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 NoteSource
Uses eval npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]

View full report↗︎

Next steps

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

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