Skip to content

[Snyk] Fix for 4 vulnerabilities#11597

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-fd4cfc9d88e5eb2d412119c1206db44d
Closed

[Snyk] Fix for 4 vulnerabilities#11597
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-fd4cfc9d88e5eb2d412119c1206db44d

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 1, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/kafka/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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  61  
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  45  

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)
🦉 Directory Traversal


EntelligenceAI PR Summary

This PR pins Backstage core dependencies to specific versions in the Kafka plugin, replacing workspace protocol references.

  • Changed @backstage/core-components from workspace:^ to fixed version 0.8.6
  • Changed @backstage/core-plugin-api from workspace:^ to fixed version 0.1.0
  • Modified in plugins/kafka/package.json
  • Transitions from monorepo workspace resolution to explicit version pinning

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 1, 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 project's security posture by resolving four identified medium-severity vulnerabilities within the plugins/kafka module's yarn dependencies. The changes involve specific version upgrades for two @backstage packages to mitigate these risks.

Highlights

  • Vulnerability Fixes: This PR addresses four medium-severity vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355), one Regular Expression Denial of Service (SNYK-JS-DIFF-14917201), and one Uncontrolled Recursion (SNYK-JS-ESLINT-15102420).
  • Dependency Updates: The plugins/kafka/package.json file has been updated to specify exact versions for @backstage/core-components (to 0.8.6) and @backstage/core-plugin-api (to 0.1.0) instead of workspace:^.
  • Yarn Zero-Install Warning: Users employing Yarn's zero-install feature will need to manually run yarn to update the .yarn/cache/ directory, as this PR does not automatically update it.
  • yarn.lock Update Failure: Snyk reported a failure to update yarn.lock, requiring manual intervention before merging.
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 1, 2026

Snyk checks have failed. 1 issues have been found so far.

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

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

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, automatically generated by Snyk, attempts to fix security vulnerabilities by updating dependencies. However, the proposed changes are incorrect for this project's monorepo structure. It replaces workspace:^ dependencies with hardcoded, outdated versions. This will break the monorepo's dependency management by fetching old packages from the public registry instead of using the local workspace packages, which will likely cause build failures and runtime issues. These changes should be rejected. The vulnerabilities should be addressed by updating the relevant packages within the workspace and then running yarn to update the lockfile correctly.

Comment on lines +29 to +30
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "0.1.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 change incorrectly replaces workspace:^ with hardcoded, outdated versions. In a monorepo using Yarn workspaces, workspace:^ is used to link to local packages. Pinning @backstage/core-components to 0.8.6 and @backstage/core-plugin-api to 0.1.0 will cause Yarn to fetch these old versions from the public registry, instead of using the versions from this repository (e.g., 0.13.4-next.0 for @backstage/core-components). This will very likely break the build or cause runtime errors due to version mismatches. This automated change from Snyk appears to be incorrect for this project's setup and should be reverted.

Suggested change
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "0.1.0",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",

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

Walkthrough

This PR updates the dependency management strategy for the Kafka plugin by transitioning from workspace protocol references to fixed version specifications for two Backstage core packages. The changes pin @backstage/core-components to version 0.8.6 and @backstage/core-plugin-api to version 0.1.0, replacing the previous workspace:^ protocol. This modification suggests a move toward explicit version control for these dependencies, potentially to ensure version stability, facilitate independent package distribution, or resolve compatibility requirements outside of the monorepo workspace environment.

Changes

File(s) Summary
plugins/kafka/package.json Updated dependency specifications for @backstage/core-components from workspace:^ to 0.8.6 and @backstage/core-plugin-api from workspace:^ to 0.1.0, pinning these packages to specific versions instead of using workspace protocol.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace Registry
    participant NPM as NPM Registry
    participant KP as Kafka Plugin

    Note over Dev,KP: Dependency Resolution Change

    Dev->>PM: Install dependencies for Kafka plugin
    
    alt Before Change (workspace:^)
        PM->>WS: Request @backstage/core-components
        WS-->>PM: Return local workspace version
        PM->>WS: Request @backstage/core-plugin-api
        WS-->>PM: Return local workspace version
    else After Change (pinned versions)
        PM->>NPM: Request @backstage/core-components@0.8.6
        NPM-->>PM: Return version 0.8.6
        PM->>NPM: Request @backstage/core-plugin-api@0.1.0
        NPM-->>PM: Return version 0.1.0
    end
    
    PM->>KP: Install resolved dependencies
    Note over KP: Plugin now uses<br/>pinned external versions<br/>instead of workspace versions
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.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 8, 2026

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 8, 2026
@github-actions github-actions Bot closed this Mar 12, 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