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] Upgrade minimatch from 3.1.2 to 10.0.1 #33

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

[Snyk] Upgrade minimatch from 3.1.2 to 10.0.1 #33

wants to merge 1 commit into from

Conversation

Sec32fun32
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade minimatch from 3.1.2 to 10.0.1.

ℹ️ 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.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 62 versions ahead of your current version.

  • The recommended version was released 6 months ago.

Release notes
Package name: minimatch
  • 10.0.1 - 2024-07-08

    10.0.1

  • 10.0.0 - 2024-07-08

    10.0.0

  • 9.0.5 - 2024-06-25

    9.0.5

  • 9.0.4 - 2024-03-28

    9.0.4

  • 9.0.3 - 2023-07-06

    9.0.3

  • 9.0.2 - 2023-06-23

    9.0.2

  • 9.0.1 - 2023-05-20

    9.0.1

  • 9.0.0 - 2023-04-09

    9.0.0

  • 8.0.4 - 2023-04-09

    8.0.4

  • 8.0.3 - 2023-04-03
  • 8.0.2 - 2023-04-02
  • 8.0.1 - 2023-04-02
  • 8.0.0 - 2023-04-02
  • 7.4.6 - 2023-04-09

    7.4.6

  • 7.4.5 - 2023-04-03
  • 7.4.4 - 2023-04-01
  • 7.4.3 - 2023-03-22
  • 7.4.2 - 2023-03-01
  • 7.4.1 - 2023-03-01
  • 7.4.0 - 2023-03-01
  • 7.3.0 - 2023-02-27
  • 7.2.0 - 2023-02-26
  • 7.1.4 - 2023-02-26
  • 7.1.3 - 2023-02-25
  • 7.1.2 - 2023-02-24
  • 7.1.1 - 2023-02-24
  • 7.1.0 - 2023-02-22
  • 7.0.1 - 2023-02-22
  • 7.0.0 - 2023-02-20
  • 6.2.0 - 2023-02-13
  • 6.1.10 - 2023-02-13
  • 6.1.9 - 2023-02-13
  • 6.1.8 - 2023-02-11
  • 6.1.7 - 2023-02-11
  • 6.1.6 - 2023-01-22
  • 6.1.5 - 2023-01-17
  • 6.1.4 - 2023-01-17
  • 6.1.3 - 2023-01-17
  • 6.1.2 - 2023-01-17
  • 6.1.1 - 2023-01-17
  • 6.1.0 - 2023-01-17
  • 6.0.4 - 2023-01-16
  • 6.0.3 - 2023-01-15
  • 6.0.2 - 2023-01-15
  • 6.0.1 - 2023-01-15
  • 6.0.0 - 2023-01-14
  • 5.1.6 - 2023-01-17
  • 5.1.5 - 2023-01-17
  • 5.1.4 - 2023-01-14
  • 5.1.3 - 2023-01-14
  • 5.1.2 - 2022-12-20
  • 5.1.1 - 2022-11-29
  • 5.1.0 - 2022-05-16
  • 5.0.1 - 2022-02-24
  • 5.0.0 - 2022-02-15
  • 4.2.3 - 2023-01-17
  • 4.2.2 - 2023-01-17
  • 4.2.1 - 2022-02-15
  • 4.2.0 - 2022-02-15
  • 4.1.1 - 2022-02-13
  • 4.1.0 - 2022-02-13
  • 4.0.0 - 2022-02-13
  • 3.1.2 - 2022-02-15
from minimatch GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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-bot
feat: upgrade minimatch from 3.1.2 to 10.0.1
30d650d 
Snyk has created this PR to upgrade minimatch from 3.1.2 to 10.0.1.

See this package in npm:
minimatch

See this project in Snyk:
https://app.snyk.io/org/sec32fun32/project/4cab838b-948d-43f5-9d34-5e7123569273?utm_source=github&utm_medium=referral&page=upgrade-pr
@socket-security Socket Security
Copy link

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

Package New capabilities Transitives Size Publisher

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[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 NoteCI
Deprecated npm/[email protected]
  • Reason: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
⚠︎
Deprecated npm/[email protected]
  • Reason: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
⚠︎
Unstable ownership npm/[email protected] ⚠︎
Unstable ownership npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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

@github-actions GitHub Actions
Copy link

Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.

@github-actions github-actions bot added the Stale label Jan 19, 2025
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
Stale
Projects
None yet
Milestone
No milestone
Development

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