[Snyk] Upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9 #99

snyk-io · 2025-04-05T17:43:34Z

Snyk has created this PR to upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9.

ℹ️ 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 3 versions ahead of your current version.
The recommended version was released 25 days ago.

Release notes

Package name: @ledgerhq/hw-app-eth

6.42.9 - 2025-03-11
6.42.9-nightly.0 - 2025-03-11
6.42.9-next.0 - 2025-03-06
6.42.8 - 2025-02-28

from @ledgerhq/hw-app-eth 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:

🧐 View latest project report

📜 Customise PR templates

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Enhancements:

Update @ledgerhq/hw-app-eth from version 6.42.8 to 6.42.9 to keep dependencies current

Snyk has created this PR to upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9. See this package in npm: @ledgerhq/hw-app-eth See this project in Snyk: https://app.snyk.io/org/dargon789/project/59c4663d-417a-416f-9dc6-c58e1e29acd9?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr

codesandbox · 2025-04-05T17:43:37Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

sourcery-ai · 2025-04-05T17:43:39Z

Reviewer's Guide by Sourcery

This pull request upgrades the @ledgerhq/hw-app-eth dependency from version 6.42.8 to 6.42.9 in packages/hardhat-ledger/package.json.

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 `@ledgerhq/hw-app-eth` dependency to version `6.42.9`. This ensures the project uses the latest features, bug fixes, and security patches from the library.	Updated the `@ledgerhq/hw-app-eth` dependency version from `6.42.8` to `6.42.9`.	`packages/hardhat-ledger/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

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

sourcery-ai

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

It seems to have been created by a bot (hey, snyk-io[bot]!). We assume it knows what it's doing!
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.

socket-security · 2025-04-05T17:44:35Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub ↗.

	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	[email protected]
	[email protected]
	[email protected]
	[email protected]

View full report ↗

socket-security · 2025-04-05T17:44:36Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub ↗.

Action	Severity	Alert (click for details)
Warn		`[email protected]` has a License Policy Violation. License: The package entry has license metadata, but it could not be parsed (npm metadata) License: BSD (package/package.json) Source: `docs/package.json` Source: `docs/pnpm-lock.yaml` Source: `docs/yarn.lock` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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 `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` has a License Policy Violation. License: CC-BY-SA-4.0 (package/LICENSE) License: CC-BY-SA-4.0 (package/LICENSE) Source: `docs/package.json` Source: `docs/pnpm-lock.yaml` Source: `docs/yarn.lock` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: 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 `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` is Deprecated. Reason: This version is no longer supported. Please see https://eslint.org/version-support for other options. Source: `docs/package.json` Source: `docs/pnpm-lock.yaml` Source: `docs/yarn.lock` ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` is Deprecated. Reason: This module is no longer supported. Source ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` is Deprecated. Reason: This package is no longer supported. Source ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` is Deprecated. Reason: Upgrade to fsevents v2 to mitigate potential security issues Source ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`[email protected]` is Deprecated. Reason: This package is no longer supported. Source ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report ↗

github-actions bot added the status:triaging label Apr 5, 2025

sourcery-ai bot reviewed Apr 5, 2025

View reviewed changes

Merge branch 'main' into snyk-upgrade-4b358ab9c61eb83bbc0d971cad8bb412

d95dbe0

Dargon789 merged commit 6d140a6 into main Apr 11, 2025
9 of 14 checks passed

Dargon789 deleted the snyk-upgrade-4b358ab9c61eb83bbc0d971cad8bb412 branch April 11, 2025 08:04

github-actions bot locked as resolved and limited conversation to collaborators Jul 11, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9 #99

[Snyk] Upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9 #99

Uh oh!

snyk-io bot commented Apr 5, 2025 •

edited by sourcery-ai bot

Loading

Uh oh!

codesandbox bot commented Apr 5, 2025

Uh oh!

sourcery-ai bot commented Apr 5, 2025 •

edited

Loading

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai bot left a comment

Uh oh!

socket-security bot commented Apr 5, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Apr 5, 2025 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

[Snyk] Upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9 #99

[Snyk] Upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9 #99

Uh oh!

Conversation

snyk-io bot commented Apr 5, 2025 • edited by sourcery-ai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Snyk has created this PR to upgrade @ledgerhq/hw-app-eth from 6.42.8 to 6.42.9.

Summary by Sourcery

Uh oh!

codesandbox bot commented Apr 5, 2025

Review or Edit in CodeSandbox

Uh oh!

sourcery-ai bot commented Apr 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide by Sourcery

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

socket-security bot commented Apr 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Apr 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

snyk-io bot commented Apr 5, 2025 •

edited by sourcery-ai bot

Loading

sourcery-ai bot commented Apr 5, 2025 •

edited

Loading

socket-security bot commented Apr 5, 2025 •

edited

Loading

socket-security bot commented Apr 5, 2025 •

edited

Loading