[Snyk] Fix for 7 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 7 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	630
	Symlink Attack SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERBACKEND-15054277	630
	Symlink Attack SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERNODE-15054276	630
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	590
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	550
	Prototype Pollution SNYK-JS-LODASH-15053838	545
	Prototype Pollution SNYK-JS-LODASHES-15053836	545

---

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
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

Migrates Backstage plugin dependencies from workspace protocol to published npm versions in the backend-next package.

• Replaced workspace:^ references with specific version numbers for 13 dependencies
• Affected packages include core backend services (backend-defaults, backend-tasks, app-backend)
• Updated catalog management dependencies (catalog-backend, catalog-backend-module-scaffolder-entity-model)
• Converted plugin backends (kubernetes, scaffolder, techdocs, todo, auth, proxy, search)
• Indicates transition from local monorepo development to production deployment configuration

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

[entelligence-ai-pr-reviews]

Walkthrough

This pull request transitions the backend-next package from using workspace protocol references to published npm package versions for Backstage dependencies. The change affects 13 plugin dependencies spanning core backend functionality, application serving, catalog management, and various plugin backends including Kubernetes, scaffolder, techdocs, and todo. This modification represents a shift from local monorepo development to consuming stable published packages, typically performed during release preparation or when configuring the application for deployment to production environments.

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, app-backend, catalog-backend, kubernetes-backend, scaffolder-backend, techdocs-backend, todo-backend, and related plugins.

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 versions for:<br/>- backend-defaults: 0.12.2<br/>- catalog-backend: 0.1.1<br/>- scaffolder-backend: 2.2.2<br/>- techdocs-backend: 0.1.1<br/>+ 6 more packages
    
    Dev->>PM: Run install command
    PM->>Registry: Resolve pinned versions
    Registry-->>PM: Return package metadata
    
    loop For each pinned dependency
        PM->>Registry: Download specific version
        Registry-->>PM: Return package tarball
    end
    
    PM->>Backend: Install dependencies
    Note over PM,Backend: Replace workspace references<br/>with versioned packages
    
    PM-->>Dev: Dependencies updated successfully
    
    Note over Dev,Backend: Result: Reproducible builds<br/>with locked dependency 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]

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!