Skip to content

[Snyk] Fix for 4 vulnerabilities#32

Open
bozza-man wants to merge 1 commit intomainfrom
snyk-fix-423368569f35ed6811cc3a75b6ed7d80
Open

[Snyk] Fix for 4 vulnerabilities#32
bozza-man wants to merge 1 commit intomainfrom
snyk-fix-423368569f35ed6811cc3a75b6ed7d80

Conversation

@bozza-man
Copy link
Member

@bozza-man bozza-man commented Jan 11, 2026

snyk-top-banner

Snyk has created this PR to fix 4 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
critical severity External Control of File Name or Path
SNYK-JS-JSPDF-14873131
  250  
high severity Cross-site Scripting (XSS)
SNYK-JS-REMIXRUNROUTER-14908530
  137  
high severity Open Redirect
SNYK-JS-REACTROUTER-14908286
  115  
high severity Open Redirect
SNYK-JS-REMIXRUNROUTER-14908287
  115  

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

Security-focused dependency upgrades with major versions and lockfile refresh.

  • Upgrade jspdf to ^4.0.0, updating transitive deps (fflate, add fast-png, optional canvg@3.0.11, dompurify@^3) and dropping legacy base64 helpers
  • Upgrade routing stack to react-router-dom@^7.0.0 (react-router@7), removing @remix-run/router and adding cookie-related deps; raises engines/peer requirements (Node >=20 for router, React >=18)
  • Lockfile updates across many packages (e.g., @babel/runtime, dompurify, compression/image libs) consistent with the above upgrades

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

@continue
Copy link

continue bot commented Jan 11, 2026

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@coderabbitai
Copy link

coderabbitai bot commented Jan 11, 2026

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@phylum-io
Copy link

phylum-io bot commented Jan 11, 2026

Phylum OSS Supply Chain Risk Analysis - FAILED

This repository analyzes the risk of new dependencies. An
administrator of this repository has set requirements via Phylum policy.

If you see this comment, one or more dependencies have failed Phylum's risk analysis.

Package: canvg@3.0.11 failed.

canvg@3.0.11 is decoding Base64 strings

Risk Domain: Malicious Code
Risk Level: low

Reason: Obfuscated code

Package: jspdf@4.0.0 failed.

jspdf@4.0.0 is decoding Base64 strings

Risk Domain: Malicious Code
Risk Level: low

Reason: Obfuscated code

Package: react-router@7.0.0 failed.

React Router vulnerable to XSS via Open Redirects

Risk Domain: Software Vulnerability
Risk Level: high

Reason: Critical or High software vulnerability

React Router has XSS Vulnerability

Risk Domain: Software Vulnerability
Risk Level: high

Reason: Critical or High software vulnerability

React Router allows pre-render data spoofing on React-Router framework mode

Risk Domain: Software Vulnerability
Risk Level: high

Reason: Critical or High software vulnerability

View this project in the Phylum UI

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bf77ea1515

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 7178 to 7180
"engines": {
"node": ">=14.0.0"
"node": ">=20.0.0"
},

Choose a reason for hiding this comment

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

P2 Badge Align Node engine with react-router v7 requirement

The upgrade pulls in react-router-dom@7, which now declares engines.node >=20 (package-lock.json lines 7178–7180). This repo explicitly pins Node 18 in package.json (lines 115–117) and .node-version (line 1). On Node 18, installs/builds can fail in environments that enforce engines (e.g., pnpm/yarn or npm with engine-strict), and even without strict enforcement you're now outside the supported runtime for the router. Consider either bumping the project’s Node version to >=20 or keeping react-router-dom on a 6.x release that supports Node 18.

Useful? React with 👍 / 👎.

"react-papaparse": "^3.18.2",
"react-redux": "^7.2.5",
"react-router-dom": "^6.1.1",
"react-router-dom": "^7.0.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 18 incompatible with react-router-dom v7 requirement

High Severity

The upgrade of react-router-dom to v7.0.0 introduces a Node.js version conflict. React Router v7 requires Node.js 20 or higher ("node": ">=20.0.0"), but the project's engines field specifies "node": "18". This will cause installation failures or runtime errors when the project is used in Node.js 18 environments.

Fix in Cursor Fix in Web

"fuzzysort": "^1.1.4",
"javascript-time-ago": "^2.5.9",
"jspdf": "^2.4.0",
"jspdf": "^4.0.0",
Copy link

Choose a reason for hiding this comment

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

jspdf-autotable incompatible with jspdf v4 peer dependency

High Severity

The upgrade of jspdf to v4.0.0 creates a peer dependency conflict. The project uses jspdf-autotable@^3.5.23, which has a peer dependency requiring jspdf@^2.5.1. Since jspdf-autotable 3.x is not designed for jspdf v4, PDF table generation functionality may break or produce runtime errors.

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.

2 participants