[Snyk] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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
 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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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 > 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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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] Fix for 2 vulnerabilities - #36

Open
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714
Open

[Snyk] Fix for 2 vulnerabilities#36
St0nersdash wants to merge 1 commit into
mainfrom
snyk-fix-4afac683c6de2df14e723d8447a4f714

Conversation

@St0nersdash

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 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
critical severityPredictable Value Range from Previous Values
SNYK-JS-FORMDATA-10841150
863
medium severityRegular Expression Denial of Service (ReDoS)
SNYK-JS-OCTOKITREQUEST-8730853
666

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)

@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.

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 two key npm dependencies: @actions/cache and @actions/github. These upgrades are specifically designed to resolve a critical 'Predictable Value Range' vulnerability and a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability, ensuring the project utilizes more secure and up-to-date library versions.

Highlights

  • Dependency Upgrades: Upgraded the @actions/cache dependency from version ^3.1.4 to ^4.0.0.
  • Dependency Upgrades: Upgraded the @actions/github dependency from version ^3.0.0 to ^6.0.0.
  • Vulnerability Fixes: Addressed a critical 'Predictable Value Range from Previous Values' vulnerability (SNYK-JS-FORMDATA-10841150) by updating dependencies.
  • Vulnerability Fixes: Addressed a medium 'Regular Expression Denial of Service (ReDoS)' vulnerability (SNYK-JS-OCTOKITREQUEST-8730853) by updating dependencies.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

@socket-security

Copy link
Copy Markdown

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

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updated@​actions/​github@​3.0.0 ⏵ 6.0.098100100+183-4100
Updated@​actions/​http-client@​2.1.1 ⏵ 2.2.310010092+184100
Updated@​actions/​core@​1.10.1 ⏵ 1.11.199+110010084100
Updated@​actions/​cache@​3.1.4 ⏵ 4.0.09810091+686+1100
Updatedtypescript@​3.8.3 ⏵ 3.9.1010010010010080

View full report

@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, automatically generated by Snyk, updates @actions/cache and @actions/github to new major versions to fix security vulnerabilities. However, these updates introduce significant breaking changes. The current codebase is not compatible with these new versions, which will break the caching functionality of this action and potentially other parts of the action. The code, including tests, needs to be updated to align with the new APIs before this PR can be merged.

Comment threadpackage.json
Comment on lines +26 to +29
"@actions/cache": "^4.0.0",
"@actions/core": "^1.10.1",
"@actions/exec": "^1.1.1",
"@actions/github": "^3.0.0",
"@actions/github": "^6.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 PR introduces major version bumps for @actions/cache (v3 to v4) and @actions/github (v3 to v6), which include breaking changes that are not handled in the current codebase.

@actions/cache v4.0.0 Breaking Change:

The cache.restoreCache() function in v4 returns a Promise<number | undefined> (the cache ID) instead of a Promise<string | undefined> (the cache key) as it did in v3. The existing code in src/cache-restore.ts and src/cache-save.ts is not compatible with this change.

Specifically:

  • In src/cache-restore.ts, the cacheKey variable now holds a cache ID, but it's used as if it were a cache key string for logging and for saving to state. The log message Cache restored from key: ${cacheKey} is now misleading.
  • In src/cache-save.ts, the logic to prevent re-saving an existing cache is broken. It compares the primaryKey (a string) with the state (which is now a cache ID), so primaryKey === state will always be false, causing the cache to be re-saved unnecessarily on every run with a cache hit.
  • The tests in __tests__/cache-restore.test.ts are also outdated, as they mock cache.restoreCache to return a string key.

@actions/github v6.0.0 Breaking Change:

This is also a major version bump with several breaking changes between v3 and v6. For example, the github.context.repo object structure has changed. While the files in this PR don't show its usage, other files in the repository (like src/installer.ts) likely use it and will need to be updated.

To fix this, the code needs to be updated to be compatible with the new APIs of these packages. Simply bumping the versions will break the action's caching functionality.

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