[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/proxy-backend/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
	Directory Traversal SNYK-JS-TAR-15127355	127
	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:

🦉 Directory Traversal

---

EntelligenceAI PR Summary

This PR pins Backstage dependencies to specific versions in the proxy-backend plugin, replacing workspace protocol references.

• Changed @backstage/backend-common from workspace:^ to fixed version 0.24.1
• Changed @backstage/config from workspace:^ to fixed version 0.1.1
• Transitions from monorepo workspace dependencies to published package versions
• Modified in plugins/proxy-backend/package.json

[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 project's security by resolving two critical vulnerabilities. It achieves this by upgrading specific @backstage dependencies within the plugins/proxy-backend module, ensuring a more secure and stable environment.

Highlights

• Dependency Updates: The @backstage/backend-common dependency has been updated from workspace:^ to 0.24.1 and the @backstage/config dependency has been updated from workspace:^ to 0.1.1 in plugins/proxy-backend/package.json.
• Vulnerability Fixes: These dependency upgrades address two identified security vulnerabilities: a Directory Traversal issue (SNYK-JS-TAR-15127355) and an Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
• Automated PR: This pull request was automatically generated by Snyk to apply the necessary security fixes.
• Yarn Zero-Install Consideration: Users leveraging Yarn's zero-install feature will need to manually run yarn to update their .yarn/cache/ directory, as this PR does not include those changes.
• Manual yarn.lock Update Required: Snyk reported a failure to update the yarn.lock file, which will require manual intervention before this PR can be merged.

Changelog

• plugins/proxy-backend/package.json
  • Updated @backstage/backend-common dependency from workspace:^ to 0.24.1.
  • Updated @backstage/config dependency from workspace:^ to 0.1.1.

Activity

• The pull request was automatically created by Snyk to address identified vulnerabilities.
• Snyk reported a warning that the yarn.lock file failed to update and requires manual intervention.

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the proxy-backend plugin by replacing workspace protocol references with fixed version numbers for two Backstage packages. The @backstage/backend-common dependency is pinned to version 0.24.1 and @backstage/config is pinned to version 0.1.1. This change transitions from using monorepo workspace dependencies (indicated by workspace:^) to explicit version specifications, which typically occurs when preparing a package for independent publication or when moving away from a monorepo structure to use published npm packages instead of local workspace references.

Changes

File(s)	Summary
plugins/proxy-backend/package.json	Replaced workspace protocol references with fixed versions for Backstage dependencies: @backstage/backend-common pinned to 0.24.1 and @backstage/config pinned to 0.1.1.

▶️ ⚡ 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.

[gemini-code-assist]

Code Review

This pull request from Snyk attempts to fix security vulnerabilities by updating dependencies. However, the proposed changes are incorrect for this monorepo setup and are likely to cause critical failures. The PR pins versions for @backstage/backend-common and @backstage/config, which breaks the workspace: protocol. Most critically, it severely downgrades @backstage/config, which will almost certainly break the application. I have added a critical review comment explaining why this PR should be rejected and suggested reverting the changes. The vulnerabilities should be addressed manually within the monorepo's structure.

[gemini-code-assist]

This automated change from Snyk is incorrect and will likely break the application. It should not be merged.

The main issues are:

1. Breaking Monorepo Structure: It replaces workspace:^ with pinned versions. This goes against the monorepo's dependency strategy and can cause version conflicts.
2. Dangerous Version Changes:
   • @backstage/config is being severely downgraded from 1.0.8 to 0.1.1, which is a critical issue.
   • @backstage/backend-common is being significantly upgraded, which introduces a high risk of breaking changes.

The correct way to fix the security vulnerabilities is to update the dependencies within their respective packages in the workspace, not to pin them here.

Suggested change

	"@backstage/backend-common": "0.24.1",
	"@backstage/backend-plugin-api": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/config": "0.1.1",
	"@backstage/backend-common": "workspace:^",
	"@backstage/backend-plugin-api": "workspace:^",
	"@backstage/config": "workspace:^",

[snyk-io]

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