Skip to content

[Snyk] Upgrade atom-package-manager from 2.6.2 to 2.6.5#765

Open
NOUIY wants to merge 1 commit intomasterfrom
snyk-upgrade-578682143c21106894be3f2f98521f01
Open

[Snyk] Upgrade atom-package-manager from 2.6.2 to 2.6.5#765
NOUIY wants to merge 1 commit intomasterfrom
snyk-upgrade-578682143c21106894be3f2f98521f01

Conversation

@NOUIY
Copy link
Owner

@NOUIY NOUIY commented Aug 10, 2024

snyk-top-banner

Snyk has created this PR to upgrade atom-package-manager from 2.6.2 to 2.6.5.

ℹ️ 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 on 3 years ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ES5EXT-6095076
482 Proof of Concept
high severity Information Exposure
SNYK-JS-SIMPLEGET-2361683
482 Proof of Concept
Release notes
Package name: atom-package-manager from atom-package-manager 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:

Snyk has created this PR to upgrade atom-package-manager from 2.6.2 to 2.6.5.

See this package in npm:
atom-package-manager

See this project in Snyk:
https://app.snyk.io/org/nexuscompute/project/0ba81923-dc32-46e9-9428-5b22caac59a6?utm_source=github&utm_medium=referral&page=upgrade-pr
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