[Snyk] Fix for 6 vulnerabilities

[q1blue]

Snyk has created this PR to fix 6 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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	208
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	113
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Prototype Pollution SNYK-JS-LODASHES-15053836	88
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

Updated Kafka plugin dependency version constraints from workspace protocol to fixed versions.

• Changed @backstage/core-components from workspace:^ to 0.1.0
• Changed @backstage/core-plugin-api from workspace:^ to 0.1.0
• Changed @backstage/plugin-catalog-react from workspace:^ to 0.0.1
• Pins dependencies to specific versions instead of using monorepo workspace resolution

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! 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 updating several key @backstage dependencies within the plugins/kafka module. These updates are crucial for resolving six identified vulnerabilities, ranging from medium to high severity, ensuring a more secure and stable development environment.

Highlights

• Dependency Updates: Updated @backstage/core-components to 0.1.0, @backstage/core-plugin-api to 0.1.0, and @backstage/plugin-catalog-react to 0.0.1 in plugins/kafka/package.json.
• Vulnerability Fixes: Addresses 6 identified vulnerabilities, including a high severity 'UNIX Symbolic Link (Symlink) Following' (SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291) and several medium severity issues such as 'Improper Handling of Unicode Encoding', 'Prototype Pollution', and 'Regular Expression Denial of Service (ReDoS)'.
• Yarn Zero-Installs Note: Includes a specific note for users of Yarn's zero-installs feature, advising that the .yarn/cache/ directory will need to be manually updated by running yarn after merging.
• Manual yarn.lock Update Required: A warning indicates that the yarn.lock file failed to update automatically and requires manual intervention before this pull request can be merged.

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]

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix several vulnerabilities by updating dependencies in plugins/kafka/package.json. However, the proposed changes are incorrect and will likely break the project. The PR replaces monorepo workspace-local dependencies (workspace:^) with very old, hardcoded versions from a public registry. This constitutes a major version downgrade and breaks the internal dependency structure of the monorepo. I have left a critical comment explaining why these changes should be reverted and how the vulnerabilities should be addressed properly. This PR should not be merged in its current state.

[gemini-code-assist]

These dependency changes are incorrect and will likely break the application. The workspace:^ protocol is used to link to other packages within this monorepo. By replacing it with very old, hardcoded versions, you are breaking this link and introducing a massive version downgrade.

For example:

• @backstage/core-components is being downgraded from a workspace version (the current version in the repo is 0.13.4-next.0) to 0.1.0.
• @backstage/core-plugin-api is being downgraded from a workspace version (current is 1.5.3) to 0.1.0.
• @backstage/plugin-catalog-react is being downgraded from a workspace version (recent versions are ~1.8.0) to 0.0.1.

This will cause major compatibility issues and almost certainly fail to build. The correct approach to fix the underlying vulnerabilities is to update the transitive dependencies that are vulnerable, not to downgrade these core packages. This PR should be rejected, and the vulnerabilities should be addressed by updating the correct packages in the monorepo. Please revert these changes.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/plugin-catalog-react": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the Kafka plugin by replacing workspace protocol references with fixed version numbers. The changes affect three Backstage dependencies: @backstage/core-components, @backstage/core-plugin-api, and @backstage/plugin-catalog-react. Instead of using the monorepo workspace resolution pattern (workspace:^), these dependencies are now pinned to specific versions (0.1.0, 0.1.0, and 0.0.1 respectively). This modification likely prepares the plugin for standalone distribution or resolves version compatibility constraints in the build/deployment pipeline.

Changes

File(s)	Summary
plugins/kafka/package.json	Updated three Backstage dependencies from workspace protocol references (workspace:^) to fixed versions: @backstage/core-components to 0.1.0, @backstage/core-plugin-api to 0.1.0, and @backstage/plugin-catalog-react to 0.0.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Package as package.json
    participant Registry as NPM Registry
    
    Note over Dev,Registry: Dependency Version Update Process
    
    Dev->>Package: Update dependency versions
    Note over Package: @backstage/core-components: workspace:^ → 0.1.0<br/>@backstage/core-plugin-api: workspace:^ → 0.1.0<br/>@backstage/plugin-catalog-react: workspace:^ → 0.0.1
    
    Dev->>Registry: Install dependencies
    Registry-->>Dev: Fetch specific versions (0.1.0, 0.1.0, 0.0.1)
    
    Note over Dev: Dependencies now pinned to<br/>specific versions instead of<br/>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.

[github-actions]

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!