Skip to content

[Snyk] Security upgrade bcrypt from 5.1.1 to 6.0.0#331

Open
DaveLuhman wants to merge 1 commit intomasterfrom
snyk-fix-da1d1a422c68f0335df79d6109122413
Open

[Snyk] Security upgrade bcrypt from 5.1.1 to 6.0.0#331
DaveLuhman wants to merge 1 commit intomasterfrom
snyk-fix-da1d1a422c68f0335df79d6109122413

Conversation

@DaveLuhman
Copy link
Owner

@DaveLuhman DaveLuhman commented Jul 12, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
  436  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

Summary by Sourcery

Upgrade bcrypt dependency from v5.1.1 to v6.0.0 to address a low-severity ReDoS security issue.

Bug Fixes:

  • Bump bcrypt to 6.0.0 to fix a Regular Expression Denial of Service vulnerability in brace-expansion.

Build:

  • Update package.json and package-lock.json with the upgraded bcrypt version.

This change is Reviewable

@sourcery-ai
Copy link

sourcery-ai bot commented Jul 12, 2025

Reviewer's Guide

This PR upgrades the bcrypt package from 5.1.1 to 6.0.0 to remediate a ReDoS vulnerability, applying the version bump and regenerating the lockfile to lock in the updated dependency.

File-Level Changes

Change Details Files
Upgrade bcrypt dependency to address security vulnerability
  • Bumped bcrypt version spec from ^5.1.1 to ^6.0.0 in package.json
  • Regenerated package-lock.json to reflect the new bcrypt version
package.json
package-lock.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!

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

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