Skip to content

[Snyk] Upgrade semver from 6.3.1 to 7.7.1 #23

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
Merged
Dargon789 merged 1 commit into from
Mar 9, 2025
Merged

[Snyk] Upgrade semver from 6.3.1 to 7.7.1 #23

Dargon789 merged 1 commit into from
Mar 9, 2025

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Mar 9, 2025 •
edited by sourcery-ai bot
Loading

snyk-top-banner

Snyk has created this PR to upgrade semver from 6.3.1 to 7.7.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 30 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: semver from semver 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:

Summary by Sourcery

Upgrade the semver dependency from version 6.3.1 to 7.7.1.

Chores:

  • Bump @ npmcli/eslint-config from 4.0.5 to 5.0.0
  • Bump @ npmcli/template-oss from 4.23.3 to 4.23.4

@snyk-bot
feat: upgrade semver from 6.3.1 to 7.7.1
435783e 
Snyk has created this PR to upgrade semver from 6.3.1 to 7.7.1.

See this package in npm:
semver

See this project in Snyk:
https://app.snyk.io/org/dargon789/project/d8b67e09-3b40-4806-96b4-f31119d86353?utm_source=github&utm_medium=referral&page=upgrade-pr
@sourcery-ai
Copy link

sourcery-ai bot commented Mar 9, 2025 •
edited
Loading

Reviewer's Guide by Sourcery

This pull request upgrades the semver dependency from version 6.3.1 to 7.7.1 by modifying the package.json file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
The pull request upgrades the semver dependency from version 6.3.1 to 7.7.1.
  • Updated the semver dependency version in package.json.
 packages/hardhat-vyper/package.json
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

sourcery-ai[bot]
sourcery-ai bot reviewed Mar 9, 2025
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

@snyk-io
Copy link

snyk-io bot commented Mar 9, 2025

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

@socket-security
Copy link

socket-security bot commented Mar 9, 2025

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

Package New capabilities Transitives Size Publisher
npm/glob@8.0.1 filesystem Transitive: environment +3 76 kB isaacs
npm/gray-matter@4.0.3 eval, filesystem 0 38.6 kB rmassaioli
npm/hastscript@7.0.2 None +4 68.6 kB wooorm

View full report↗︎

@socket-security
Copy link

socket-security bot commented Mar 9, 2025

🚨 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 NoteSourceCI
Deprecated npm/inflight@1.0.6
  • 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/is-accessor-descriptor@0.1.6
  • Reason: Please upgrade to v0.1.7
 ⚠︎
Deprecated npm/is-accessor-descriptor@1.0.0
  • Reason: Please upgrade to v1.0.1
 ⚠︎
License Policy Violation npm/glob@7.1.7
  • License: CC-BY-SA-4.0 (package/LICENSE)
  • License: CC-BY-SA-4.0 (package/LICENSE)
 ⚠︎
Deprecated npm/gauge@3.0.2
  • Reason: This package is no longer supported.
 ⚠︎
Deprecated npm/figgy-pudding@3.5.2
  • Reason: This module is no longer supported.
 ⚠︎
Deprecated npm/fs-write-stream-atomic@1.0.10
  • Reason: This package is no longer supported.
 ⚠︎
License Policy Violation npm/glob-to-regexp@0.3.0
  • License: The package entry has license metadata, but it could not be parsed (npm metadata)
  • License: BSD (package/package.json)
 ⚠︎
High CVE npm/ip@1.1.9 ⚠︎
Deprecated npm/fsevents@1.2.13
  • Reason: Upgrade to fsevents v2 to mitigate potential security issues
 ⚠︎

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 a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/inflight@1.0.6
  • @SocketSecurity ignore npm/is-accessor-descriptor@0.1.6
  • @SocketSecurity ignore npm/is-accessor-descriptor@1.0.0
  • @SocketSecurity ignore npm/glob@7.1.7
  • @SocketSecurity ignore npm/gauge@3.0.2
  • @SocketSecurity ignore npm/figgy-pudding@3.5.2
  • @SocketSecurity ignore npm/fs-write-stream-atomic@1.0.10
  • @SocketSecurity ignore npm/glob-to-regexp@0.3.0
  • @SocketSecurity ignore npm/ip@1.1.9
  • @SocketSecurity ignore npm/fsevents@1.2.13

@Dargon789 Dargon789 merged commit 9204ad7 into main Mar 9, 2025
16 of 32 checks passed
@Dargon789 Dargon789 deleted the snyk-upgrade-5ee00a1e83cfc32c09337837a92b110c branch March 9, 2025 20:02
This was linked to issues Mar 9, 2025
Fix code scanning alert - Checkout of untrusted code in trusted context #29
Closed
Fix code scanning alert - Checkout of untrusted code in trusted context #28
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

Assignees

No one assigned

Labels

status:ready

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Fix code scanning alert - Checkout of untrusted code in trusted context Fix code scanning alert - Checkout of untrusted code in trusted context

3 participants

@Dargon789 @snyk-bot