[Snyk] Fix for 10 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• packages/backend-next/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
	Symlink Attack SNYK-JS-BACKSTAGEBACKENDDEFAULTS-15054278	322
	Symlink Attack SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERBACKEND-15054277	322
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	263
	Symlink Attack SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERNODE-15054276	242
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	182
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	141
	Prototype Pollution SNYK-JS-LODASH-15053838	110
	Prototype Pollution SNYK-JS-LODASHES-15053836	110
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	77
	Server-side Request Forgery (SSRF) SNYK-JS-BACKSTAGEBACKENDDEFAULTS-15064476	68

---

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:

🦉 Symlink Attack
🦉 Server-side Request Forgery (SSRF)
🦉 Regular Expression Denial of Service (ReDoS)
🦉 More lessons are available in Snyk Learn

---

EntelligenceAI PR Summary

This PR stabilizes dependencies in the backend-next package by replacing workspace references with specific published versions.

• Updated 13 Backstage plugin dependencies from workspace:^ to specific version numbers
• Affected packages include core backend functionality (backend-defaults, backend-tasks)
• Updated various plugin backends (catalog, scaffolder, techdocs, kubernetes)
• Updated common modules and shared dependencies
• Indicates transition from local monorepo development to consuming released package versions

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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]

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 bolster the project's security by resolving 10 identified vulnerabilities within its Yarn dependencies. It primarily updates various @backstage packages in the packages/backend-next/package.json file to their latest secure versions, mitigating risks such as Symlink Attacks, Prototype Pollution, and Regular Expression Denial of Service. Reviewers should note the requirement for a manual yarn.lock update.

Highlights

• Dependency Updates: Several @backstage packages in packages/backend-next/package.json have been updated to specific, newer versions to resolve identified security vulnerabilities.
• Vulnerability Remediation: This pull request addresses 10 vulnerabilities, including high-severity Symlink Attacks and medium-severity Prototype Pollution and Regular Expression Denial of Service (ReDoS) issues.
• Manual yarn.lock Update Required: The yarn.lock file was not automatically updated by Snyk, requiring manual intervention to ensure dependency consistency after merging this PR.

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 pull request updates the dependency management strategy for the backend-next package by replacing workspace protocol references with specific published versions. Thirteen Backstage plugin dependencies are affected, spanning core backend functionality, plugin backends, and common modules. The change transitions from local monorepo development dependencies (workspace:^) to consuming specific released versions of packages including backend-defaults, backend-tasks, catalog, scaffolder, techdocs, kubernetes, and others. This modification typically indicates preparation for a release, dependency stabilization, or a shift from development to production-ready dependency management.

Changes

File(s)	Summary
packages/backend-next/package.json	Converted 13 Backstage plugin dependencies from workspace protocol references (workspace:^) to specific published versions, including backend-defaults, backend-tasks, catalog, scaffolder, techdocs, kubernetes, and other plugin backends and common modules.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    participant Backend as backend-next Package

    Dev->>PM: Update package.json dependencies
    Note over Dev,PM: Pin workspace dependencies<br/>to specific versions
    
    PM->>Registry: Resolve dependency versions
    Note over Registry: @backstage/backend-defaults: 0.12.2<br/>@backstage/plugin-catalog-backend: 0.1.1<br/>@backstage/plugin-scaffolder-backend: 2.2.2<br/>and 8 other packages
    
    Registry-->>PM: Return package metadata
    
    PM->>Backend: Install pinned dependencies
    activate Backend
    
    loop For each updated dependency
        PM->>Registry: Download package
        Registry-->>PM: Package tarball
        PM->>Backend: Install to node_modules
    end
    
    Backend-->>PM: Dependencies installed
    deactivate Backend
    
    PM-->>Dev: Installation complete
    
    Note over Dev,Backend: Dependencies now use 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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by updating dependencies. However, the approach taken is not suitable for this monorepo. It replaces workspace:^ specifiers with pinned versions in packages/backend-next/package.json, which breaks the internal dependency linking of the Yarn workspace. This is a critical issue that would disrupt the development workflow and lead to inconsistencies. My review includes a detailed comment explaining the problem and recommending the correct approach to apply these security fixes without breaking the monorepo structure. The PR also failed to update the yarn.lock file, which needs to be addressed manually.

[gemini-code-assist]

This automated change from Snyk incorrectly modifies the dependency management for this monorepo. By replacing workspace:^ with pinned versions, it breaks the Yarn workspace linking.

Problem:
In a monorepo configured with Yarn workspaces, workspace:^ ensures that local packages depend on the code of other packages within the same monorepo. Pinning to a specific version (e.g., "@backstage/backend-defaults": "0.12.2") forces Yarn to fetch that version from the package registry, ignoring any local changes made to the @backstage/backend-defaults package. This can lead to:

• Developers testing against outdated or incorrect versions of internal packages.
• Inconsistent behavior between local development and CI/CD builds.
• Difficult-to-diagnose bugs.

The PR description itself warns: Failed to update the yarn.lock, please update manually before merging. This is a strong indicator that the automated process did not handle the monorepo structure correctly.

Recommendation:
These changes should not be merged as they are. The correct way to address the vulnerabilities is to:

1. Identify which packages within the workspace need updating.
2. Update the version field in the package.json of those specific packages.
3. Run yarn install to update the yarn.lock file and ensure all workspace packages resolve to the correct local versions.

This will fix the vulnerabilities while preserving the integrity of the monorepo setup.