[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all \u003cpre\u003e\u003ccode\u003e blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks"); } } catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); } })(); (function(){ try { var __m = "github.com"; var __re = new RegExp('^' + "github\\.com" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length \u003e 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0 - #38

Merged
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1
Feb 20, 2026
Merged

[Snyk] Security upgrade jest from 29.6.0 to 30.0.0#38
St0nersdash merged 1 commit into
mainfrom
snyk-fix-1df5580521202c65dcd119385bc060f1

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

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:

IssueScore
medium severityPrototype Pollution
SNYK-JS-JSYAML-13961110
545

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:

🦉 Prototype Pollution

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @St0nersdash, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

  • Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
  • Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
  • Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

FeatureCommandDescription
Code Review/gemini reviewPerforms a code review for the current pull request in its current state.
Pull Request Summary/gemini summaryProvides a summary of the current pull request in its current state.
Comment@gemini-code-assistResponds in comments when explicitly tagged, both in pull request comments and review comments.
Help/gemini helpDisplays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assistgemini-code-assistBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

Comment threadpackage.json
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^29.6.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

  • @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
  • ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
  • jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
"@types/jest": "^29.5.11",
"@types/node": "^16.11.25",
"@types/semver": "^6.0.0",
"@vercel/ncc": "^0.33.4",
"jest": "^30.0.0",
"prettier": "^1.19.1",
"ts-jest": "^29.1.2",
"typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatedjest@​29.6.0 ⏵ 30.0.0100+110067-197+5100
Updatedsemver@​7.7.1 ⏵ 7.7.3100+1100100+189100

View full report

@St0nersdash
St0nersdash merged commit 02d991b into mainFeb 20, 2026
88 of 140 checks passed
Sign up for freeto 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

@St0nersdash@snyk-bot