Skip to content

[Snyk] Fix for 3 vulnerabilities#12082

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-18becd2a062766bfb630cd4e68849c61
Closed

[Snyk] Fix for 3 vulnerabilities#12082
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-18becd2a062766bfb630cd4e68849c61

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/events-backend-module-github/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  83  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  83  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  62  

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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR transitions the events-backend-module-github plugin from workspace protocol dependencies to pinned version numbers.

  • Updated @backstage/backend-plugin-api to version 0.6.19
  • Updated @backstage/config to version 0.1.1
  • Updated @backstage/plugin-events-node to version 0.2.9
  • Changes made only in package.json dependency declarations
  • No functional code changes included

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, 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 security posture of the project by resolving three identified vulnerabilities. It achieves this by upgrading specific @backstage dependencies within the plugins/events-backend-module-github/package.json file. Reviewers should pay close attention to the required manual update of the yarn.lock file to ensure a smooth integration.

Highlights

  • Security Vulnerability Fixes: This pull request addresses three security vulnerabilities: two Server-side Request Forgery (SSRF) issues (SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969) and one Allocation of Resources Without Limits or Throttling issue (SNYK-JS-QS-15268416).
  • Dependency Updates: The @backstage/backend-plugin-api, @backstage/config, and @backstage/plugin-events-node dependencies have been updated to specific versions (0.6.19, 0.1.1, and 0.2.9 respectively) in plugins/events-backend-module-github/package.json.
  • Manual yarn.lock Update Required: Snyk failed to update the yarn.lock file, which requires manual intervention to ensure all dependencies are correctly resolved after merging this PR, especially for projects using Yarn's zero-installs feature.
Changelog
  • plugins/events-backend-module-github/package.json
    • Updated @backstage/backend-plugin-api from workspace:^ to 0.6.19.
    • Updated @backstage/config from workspace:^ to 0.1.1.
    • Updated @backstage/plugin-events-node from workspace:^ to 0.2.9.
Activity
  • This pull request was automatically created by Snyk to fix identified security vulnerabilities.
  • Snyk reported that it was unable to update the yarn.lock file, indicating a manual update is necessary.
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.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays 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.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR updates the dependency management strategy for the events-backend-module-github plugin by replacing workspace protocol references with explicit version numbers. Three Backstage packages are affected: @backstage/backend-plugin-api (pinned to 0.6.19), @backstage/config (pinned to 0.1.1), and @backstage/plugin-events-node (pinned to 0.2.9). This transition from monorepo workspace dependencies to fixed versions suggests preparation for independent package publishing or establishing stricter version control. The changes are purely declarative, affecting only the package.json dependency specifications without any functional code modifications.

Changes

File(s) Summary
plugins/events-backend-module-github/package.json Replaced workspace protocol references with explicit version numbers for three dependencies: @backstage/backend-plugin-api (0.6.19), @backstage/config (0.1.1), and @backstage/plugin-events-node (0.2.9).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant EBMG as events-backend-module-github
    participant BPA as @backstage/backend-plugin-api
    participant BC as @backstage/config
    participant PEN as @backstage/plugin-events-node

    Note over PM,PEN: Dependency Resolution During Installation

    PM->>EBMG: Install package
    EBMG->>PM: Request dependencies
    PM->>BPA: Resolve version 0.6.19
    BPA-->>PM: Package resolved
    PM->>BC: Resolve version 0.1.1
    BC-->>PM: Package resolved
    PM->>PEN: Resolve version 0.2.9
    PEN-->>PM: Package resolved
    PM-->>EBMG: Dependencies installed

    Note over EBMG: Now uses fixed versions<br/>instead of workspace references
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@socket-security
Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedreact@​17.0.21001007897100
Addedstorybook-dark-mode@​1.1.29910010080100
Addedswc-loader@​0.2.31001009285100
Addedreact-hot-loader@​4.13.19710010085100
Addedtypescript@​4.7.410010010010080
Addedreact-dom@​17.0.21001009098100

View full report

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: storybook/package.jsonnpm/typescript@4.7.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.7.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

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 aims to address three reported vulnerabilities by upgrading key dependencies in plugins/events-backend-module-github/package.json. While the dependency updates are a positive step towards improving security, the PR description indicates that the yarn.lock file was not updated. This is a critical oversight that prevents the security fixes from being fully applied and could lead to inconsistent dependency resolution. It is essential to update yarn.lock to reflect these changes before merging.

Comment on lines +38 to +40
"@backstage/backend-plugin-api": "0.6.19",
"@backstage/config": "0.1.1",
"@backstage/plugin-events-node": "0.2.9",
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

These dependency upgrades are crucial for addressing the reported vulnerabilities. However, the PR description indicates that yarn.lock failed to update. For these changes to be fully effective and to ensure consistent builds, the yarn.lock file must also be updated to reflect these new versions. Please run yarn install to regenerate the lock file before merging.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants