Skip to content

Conversation

@DMontgomery40
Copy link
Owner

@DMontgomery40 DMontgomery40 commented Jan 16, 2026

snyk-top-banner

Snyk has created this PR to fix 5 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
high severity Cross-site Scripting (XSS)
SNYK-JS-REACTROUTER-14908531
  646  
high severity Open Redirect
SNYK-JS-REACTROUTER-14908286
  641  
medium severity Cross-site Request Forgery (CSRF)
SNYK-JS-REACTROUTER-14908429
  631  
medium severity Cross-site Scripting (XSS)
SNYK-JS-REACTROUTER-14908293
  601  
medium severity Cross-site Scripting (XSS)
SNYK-JS-REACTROUTER-14908289
  596  

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:

🦉 Open Redirect
🦉 Cross-site Scripting (XSS)


Note

Dependency upgrades to address security vulnerabilities

  • Bumps react-router-dom from ^7.5.2 to ^7.12.0 in package.json and lockfile
  • Updates transitive deps: react-router7.12.0, cookie1.1.1, set-cookie-parser2.7.2; removes turbo-stream
  • No source code changes; only dependency/version updates

Written by Cursor Bugbot for commit 862b115. This will update automatically on new commits. Configure here.

@netlify
Copy link

netlify bot commented Jan 16, 2026

Deploy Preview for securitylends ready!

Name Link
🔨 Latest commit 862b115
🔍 Latest deploy log https://app.netlify.com/projects/securitylends/deploys/696a24923c805b00085af874
😎 Deploy Preview https://deploy-preview-31--securitylends.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 99 (🔴 down 1 from production)
Accessibility: 83 (no change from production)
Best Practices: 100 (no change from production)
SEO: 80 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

"cookie": "^1.0.1",
"set-cookie-parser": "^2.6.0",
"turbo-stream": "2.4.0"
"set-cookie-parser": "^2.6.0"
Copy link

Choose a reason for hiding this comment

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

Node.js version mismatch breaks CI/CD builds

High Severity

The react-router-dom upgrade to 7.12.0 introduces a dependency (react-router 7.12.0) that requires Node.js >= 20.0.0, but the project's CI/CD infrastructure is configured to use Node.js 18. The GitHub Actions workflow uses node-version: '18' and netlify.toml sets NODE_VERSION = "18". This version mismatch will cause npm engine warnings and may result in build failures or unexpected behavior during deployment.

Fix in Cursor Fix in Web

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.

3 participants