[Snyk] Fix for 2 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/techdocs-module-addons-contrib/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-AJV-15274295	685
	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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR transitions the techdocs-module-addons-contrib plugin from workspace protocol dependencies to fixed semantic versions.

• Changed @backstage/core-components from workspace:^ to 0.1.0
• Changed @backstage/integration-react from workspace:^ to 0.1.1
• Changed @backstage/plugin-techdocs-react from workspace:^ to 0.1.0
• Indicates transition from monorepo workspace dependencies 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 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 techdocs-module-addons-contrib plugin by replacing workspace protocol references with fixed semantic versions. Three Backstage packages are affected: @backstage/core-components is pinned to version 0.1.0, @backstage/integration-react to version 0.1.1, and @backstage/plugin-techdocs-react to version 0.1.0. This transition from workspace:^ protocol to explicit version numbers suggests preparation for package publication or a shift in dependency management approach, moving away from monorepo workspace dependencies to published package versions.

Changes

File(s)	Summary
plugins/techdocs-module-addons-contrib/package.json	Updated three Backstage package dependencies from workspace protocol (workspace:^) to fixed semantic versions: @backstage/core-components to 0.1.0, @backstage/integration-react to 0.1.1, and @backstage/plugin-techdocs-react to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant TDA as techdocs-module-addons-contrib
    participant CC as @backstage/core-components
    participant IR as @backstage/integration-react
    participant PTR as @backstage/plugin-techdocs-react
    
    Note over PM,PTR: Dependency Resolution Process
    
    PM->>TDA: Install dependencies
    
    Note over TDA: Before: workspace:^ references<br/>After: Fixed versions
    
    TDA->>CC: Request @backstage/core-components
    alt After Change
        CC-->>TDA: Return v0.1.0 (pinned)
    else Before Change
        CC-->>TDA: Return workspace version
    end
    
    TDA->>IR: Request @backstage/integration-react
    alt After Change
        IR-->>TDA: Return v0.1.1 (pinned)
    else Before Change
        IR-->>TDA: Return workspace version
    end
    
    TDA->>PTR: Request @backstage/plugin-techdocs-react
    alt After Change
        PTR-->>TDA: Return v0.1.0 (pinned)
    else Before Change
        PTR-->>TDA: Return workspace version
    end
    
    TDA-->>PM: Dependencies resolved
    Note over PM,PTR: Build can now use specific 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.

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