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 eslint from 8.57.0 to 9.0.0 #52

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

[Snyk] Security upgrade eslint from 8.57.0 to 9.0.0 #52

wants to merge 1 commit into from

Conversation

naiba4
Copy link
Owner

@naiba4 naiba4 commented Apr 6, 2024

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:
    • packages/scripts/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 141/1000
Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Local, EPSS: 0.01055, Social Trends: No, Days since published: 127, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.35, Score Version: V5		 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: eslint The new version differs by 231 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.

@vercel Vercel
Copy link

vercel bot commented Apr 6, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gutenberg ❌ Failed (Inspect) Apr 6, 2024 7:31am
gutenberg-wd9x ❌ Failed (Inspect) Apr 6, 2024 7:31am

@pull-request-quantifier-deprecated Pull Request Quantifier (deprecated)
Copy link

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details 

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 6, 2024

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

  • Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
  • Labels found: Extra Small.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

@socket-security Socket Security
Copy link

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

Package New capabilities Transitives Size Publisher
npm/@actions/[email protected] environment, filesystem Transitive: network +2 260 kB thboop
npm/@actions/[email protected] environment, filesystem Transitive: network +13 4.49 MB thboop
npm/@ariakit/[email protected] None +5 3.57 MB ariakit-bot
npm/@ariakit/[email protected] None +1 1.46 MB ariakit-bot
npm/@axe-core/[email protected] None 0 44.4 kB npmdeque
npm/@babel/[email protected] environment, filesystem, unsafe +32 8.06 MB nicolo-ribaudo
npm/@babel/[email protected] unsafe +1 127 kB nicolo-ribaudo
npm/@babel/[email protected] None +2 18.8 kB nicolo-ribaudo
npm/@babel/[email protected] None +1 14.6 kB nicolo-ribaudo
npm/@babel/[email protected] unsafe Transitive: environment +5 2.57 MB nicolo-ribaudo
npm/@babel/[email protected] None 0 216 kB nicolo-ribaudo
npm/@babel/[email protected] Transitive: environment +18 5.56 MB nicolo-ribaudo
npm/@emotion/[email protected] environment +7 2.78 MB emotion-release-bot
npm/@emotion/[email protected] environment +3 151 kB emotion-release-bot
npm/@emotion/[email protected] environment +10 3.2 MB emotion-release-bot
npm/@emotion/[email protected] environment +2 144 kB emotion-release-bot
npm/@emotion/[email protected] environment +3 212 kB emotion-release-bot
npm/@emotion/[email protected] environment +2 587 kB emotion-release-bot
npm/@emotion/[email protected] environment +1 65.6 kB emotion-release-bot
npm/@emotion/[email protected] environment +1 227 kB emotion-release-bot
npm/@emotion/[email protected] environment 0 18.3 kB emotion-release-bot
npm/@geometricpanda/[email protected] Transitive: environment, eval, filesystem, network, unsafe +48 10.1 MB geometricpandadev
npm/@octokit/[email protected] None 0 21.9 kB octokitbot
npm/@octokit/[email protected] Transitive: network +6 2.81 MB octokitbot
npm/@octokit/[email protected] None +1 1.76 MB octokitbot
npm/@octokit/[email protected] None 0 162 kB octokitbot
npm/@octokit/[email protected] None 0 210 kB octokitbot
npm/@playwright/[email protected] None 0 25.3 kB aslushnikov
npm/@pmmmwh/[email protected] environment, filesystem Transitive: network +2 441 kB pmmmwh
npm/@react-native-clipboard/[email protected] None 0 176 kB naturalclar
npm/@react-native-community/[email protected] None 0 300 kB titozzz
npm/@react-native-masked-view/[email protected] None 0 58.2 kB naturalclar
npm/@react-native/[email protected] None 0 155 kB react-native-bot
npm/@react-navigation/[email protected] environment 0 971 kB satya164
npm/@react-navigation/[email protected] environment +3 1.49 MB satya164
npm/@react-navigation/[email protected] None 0 237 kB satya164
npm/@react-navigation/[email protected] Transitive: environment +1 1.14 MB satya164
npm/@react-spring/[email protected] environment +5 448 kB tdfka_rick
npm/@storybook/[email protected] Transitive: environment, eval, network +42 8.7 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, network +39 8.51 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, filesystem, network, unsafe +48 10 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, filesystem, network, unsafe +79 23.5 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, network +39 8.49 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, network +39 8.5 MB shilman
npm/@storybook/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +122 21.3 MB shilman
npm/@storybook/[email protected] Transitive: environment, filesystem, network, unsafe +16 3.94 MB shilman
npm/@storybook/[email protected] filesystem +3 351 kB shilman

🚮 Removed packages: npm/@docusaurus/[email protected], npm/@docusaurus/[email protected], npm/@docusaurus/[email protected], npm/@mdx-js/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Network access npm/[email protected]
Network access npm/[email protected]
Network access npm/[email protected]
Uses eval npm/[email protected]
Uses eval npm/[email protected]
Uses eval npm/[email protected]
Uses eval npm/[email protected]
New author npm/[email protected]
Network access npm/[email protected]
Shell 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]
  • Env Vars: npm_package_config_puppeteer_executable_path
  • Location: Package overview
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
High entropy strings npm/[email protected]
High entropy strings npm/[email protected]
Environment variable access npm/[email protected]
Debug access npm/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Unmaintained npm/[email protected]
  • Last Publish: 11/10/2018, 2:38:01 AM
New author npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
New author npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Network access npm/[email protected]
Network access npm/[email protected]
Network access npm/[email protected]
Network access npm/[email protected]
Filesystem access npm/@kwsites/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
Minified code npm/[email protected]
Dynamic require npm/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
Filesystem access npm/[email protected]
Filesystem access npm/[email protected]
New author npm/[email protected]
Network access npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Shell access npm/@aw-web-design/[email protected]
Deprecated npm/@babel/[email protected]
  • Reason: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
Environment variable access

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
Extra Small
Projects
None yet
Milestone
No milestone
Development

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