[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/azure-devops-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
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	590

---

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:

🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR transitions the Azure DevOps backend plugin from workspace dependencies to fixed package versions.

• Changed @backstage/backend-common from workspace:^ to version 0.24.1
• Changed @backstage/backend-plugin-api from workspace:^ to version 0.6.19
• Changed @backstage/plugin-azure-devops-common from workspace:^ to version 0.0.1
• Changed express from workspace:^ to version ^4.22.0
• Indicates preparation for plugin release or dependency stabilization

[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 Azure DevOps backend plugin's dependency management strategy by transitioning from workspace protocol references to specific published package versions. Four key dependencies are affected: @backstage/backend-common (0.24.1), @backstage/backend-plugin-api (0.6.19), @backstage/plugin-azure-devops-common (0.0.1), and express (^4.22.0). This change represents a shift from local workspace dependencies to fixed version numbers, which is a common practice when preparing a plugin for production release, ensuring version stability, or making the package independently distributable outside of a monorepo workspace environment.

Changes

File(s)	Summary
plugins/azure-devops-backend/package.json	Updated four dependencies from workspace protocol references to specific version numbers: @backstage/backend-common to 0.24.1, @backstage/backend-plugin-api to 0.6.19, @backstage/plugin-azure-devops-common to 0.0.1, and express to ^4.22.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client
    participant AzureDevOpsBackend as Azure DevOps Backend Plugin
    participant BackendAPI as Backend Plugin API
    participant BackendCommon as Backend Common
    participant Express
    participant AzureAPI as Azure DevOps API

    Note over AzureDevOpsBackend: Dependency versions updated:<br/>backend-common: 0.24.1<br/>backend-plugin-api: 0.6.19<br/>express: 4.22.0

    Client->>AzureDevOpsBackend: HTTP Request
    activate AzureDevOpsBackend
    
    AzureDevOpsBackend->>Express: Route request via express-promise-router
    activate Express
    
    AzureDevOpsBackend->>BackendAPI: Use plugin API interfaces
    activate BackendAPI
    BackendAPI-->>AzureDevOpsBackend: Plugin context
    deactivate BackendAPI
    
    AzureDevOpsBackend->>BackendCommon: Utilize common backend utilities
    activate BackendCommon
    BackendCommon-->>AzureDevOpsBackend: Common services
    deactivate BackendCommon
    
    AzureDevOpsBackend->>AzureAPI: Query Azure DevOps (via azure-devops-node-api)
    activate AzureAPI
    AzureAPI-->>AzureDevOpsBackend: Azure DevOps data
    deactivate AzureAPI
    
    Express-->>Client: HTTP Response
    deactivate Express
    deactivate AzureDevOpsBackend

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!