Skip to content

[Snyk] Upgrade shx from 0.2.2 to 0.4.0 - #324

Open
ccs-snyk wants to merge 1 commit into
developmentfrom
snyk-upgrade-6a88a49718342978f4cddb99baf26dfb
Open

[Snyk] Upgrade shx from 0.2.2 to 0.4.0#324
ccs-snyk wants to merge 1 commit into
developmentfrom
snyk-upgrade-6a88a49718342978f4cddb99baf26dfb

Conversation

@ccs-snyk

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade shx from 0.2.2 to 0.4.0.

ℹ️ 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 6 versions ahead of your current version.

  • The recommended version was released a year ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Improper Privilege Management
SNYK-JS-SHELLJS-2332187
131 Proof of Concept
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
131 Proof of Concept
Release notes
Package name: shx from shx 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.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

@ccs-snyk

ccs-snyk commented May 16, 2026

Copy link
Copy Markdown
Author

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

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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