[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/integration-react/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
	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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

This PR transitions dependency management from workspace protocol references to explicit semantic version pinning for the integration-react package.

• Changed @backstage/config from workspace:^ to version 0.1.1
• Changed @backstage/core-components, @backstage/core-plugin-api, and @backstage/integration from workspace:^ to version 0.1.0
• Retained workspace protocol for @backstage/theme dependency
• Indicates preparation for package release or dependency management policy update

[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 PR updates the dependency management strategy for the @backstage/integration-react package by transitioning from workspace protocol references to explicit semantic version pinning. Four Backstage dependencies are affected: @backstage/config is pinned to version 0.1.1, while @backstage/core-components, @backstage/core-plugin-api, and @backstage/integration are pinned to version 0.1.0. The @backstage/theme dependency continues to use the workspace protocol. This change suggests preparation for package release or alignment with a new dependency management policy, moving away from monorepo workspace dependency resolution to explicit version control.

Changes

File(s)	Summary
packages/integration-react/package.json	Updated dependency version constraints from workspace protocol (workspace:^) to explicit semantic versions: @backstage/config pinned to 0.1.1, and @backstage/core-components, @backstage/core-plugin-api, @backstage/integration pinned to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace
    participant NPM as NPM Registry
    participant App as integration-react

    Dev->>PM: Run build/install command
    
    Note over PM,App: Before: workspace:^ dependencies
    PM->>WS: Resolve @backstage/config (workspace:^)
    WS-->>PM: Return local workspace version
    PM->>WS: Resolve @backstage/core-components (workspace:^)
    WS-->>PM: Return local workspace version
    
    Note over PM,NPM: After: Fixed version dependencies
    PM->>NPM: Fetch @backstage/config@0.1.1
    NPM-->>PM: Return version 0.1.1
    PM->>NPM: Fetch @backstage/core-components@0.1.0
    NPM-->>PM: Return version 0.1.0
    PM->>NPM: Fetch @backstage/core-plugin-api@0.1.0
    NPM-->>PM: Return version 0.1.0
    PM->>NPM: Fetch @backstage/integration@0.1.0
    NPM-->>PM: Return version 0.1.0
    
    PM->>App: Install resolved dependencies
    App-->>Dev: Build ready with fixed 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!