[Snyk] Fix for 4 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 4 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
	Prototype Pollution SNYK-JS-AXIOS-15252993	710
	Improper Handling of Exceptional Conditions SNYK-JS-OCTOKIT-6129525	710
	Improper Handling of Exceptional Conditions SNYK-JS-OCTOKITWEBHOOKS-6129527	710
	Arbitrary Code Injection SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERBACKEND-5730767	700

---

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:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

---

EntelligenceAI PR Summary

Updated dependency resolution strategy for three Backstage plugins in backend-next package from workspace references to fixed npm versions.

• Changed @backstage/plugin-scaffolder-backend from workspace:^ to 1.15.0
• Changed @backstage/plugin-search-backend-module-techdocs from workspace:^ to 0.1.0
• Changed @backstage/plugin-techdocs-backend from workspace:^ to 0.1.1
• Transitions from local workspace references to published package versions

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for three Backstage plugins in the backend-next package. The changes transition from using workspace protocol references (workspace:^) to fixed version numbers, pinning @backstage/plugin-scaffolder-backend to version 1.15.0, @backstage/plugin-search-backend-module-techdocs to version 0.1.0, and @backstage/plugin-techdocs-backend to version 0.1.1. This modification replaces local workspace references with published npm package versions, likely in preparation for package publication or to resolve workspace dependency resolution issues in the monorepo structure.

Changes

File(s)	Summary
packages/backend-next/package.json	Updated three Backstage plugin dependencies from workspace protocol (workspace:^) to fixed versions: @backstage/plugin-scaffolder-backend to 1.15.0, @backstage/plugin-search-backend-module-techdocs to 0.1.0, and @backstage/plugin-techdocs-backend to 0.1.1.

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

    Note over Dev,Backend: Dependency Version Pinning Change

    Dev->>Backend: Update package.json<br/>(pin 3 dependencies to specific versions)
    
    Note over Backend: Changes:<br/>- scaffolder-backend: workspace → 1.15.0<br/>- search-module-techdocs: workspace → 0.1.0<br/>- techdocs-backend: workspace → 0.1.1

    Dev->>PM: Run npm/yarn install
    
    alt Previously (workspace:^)
        PM->>Backend: Resolve from local workspace
        Note over PM,Backend: Uses local development versions
    else After Change (specific versions)
        PM->>Registry: Fetch specific versions
        Registry-->>PM: Return pinned packages
        PM->>Backend: Install exact versions
        Note over PM,Backend: Uses published registry versions
    end

    Note over Dev,Backend: No runtime behavior changes<br/>Only affects dependency resolution

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!