[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/techdocs-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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	685

---

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)

---

EntelligenceAI PR Summary

This PR converts workspace protocol dependencies to explicit version pinning in the techdocs-backend plugin package configuration.

• Replaced workspace:^ with pinned version 0.24.1 for @backstage/backend-common
• Replaced workspace:^ with pinned version 0.1.1 for @backstage/catalog-model
• Replaced workspace:^ with pinned version 0.1.0 for @backstage/plugin-catalog-common
• Replaced workspace:^ with pinned version 0.4.0 for @backstage/plugin-search-backend-module-techdocs
• Replaced workspace:^ with pinned version 0.3.1 for @backstage/plugin-search-common

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react@​17.0.2
	storybook-dark-mode@​1.1.2
	swc-loader@​0.2.3
	react-hot-loader@​4.13.1
	typescript@​4.7.4
	react-dom@​17.0.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm typescript under W3C-20150513 License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) From: storybook/package.json → npm/typescript@4.7.4 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.7.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management strategy for the techdocs-backend plugin by replacing workspace protocol references with explicit version pinning. Five Backstage packages are affected: backend-common, catalog-model, plugin-catalog-common, plugin-search-backend-module-techdocs, and plugin-search-common. The change transitions from using workspace:^ references (typical in monorepo setups) to specific pinned versions, which provides more predictable dependency resolution and is commonly done when preparing packages for independent release or implementing stricter dependency management policies.

Changes

File(s)	Summary
plugins/techdocs-backend/package.json	Converted five Backstage package dependencies from workspace protocol references (workspace:^) to pinned versions: @backstage/backend-common (0.24.1), @backstage/catalog-model (0.1.1), @backstage/plugin-catalog-common (0.1.0), @backstage/plugin-search-backend-module-techdocs (0.4.0), and @backstage/plugin-search-common (0.3.1).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant TDB as techdocs-backend
    participant BC as backend-common
    participant CM as catalog-model
    participant CC as catalog-common
    participant SM as search-module-techdocs
    participant SC as search-common
    
    Note over PM,SC: Dependency Version Update Process
    
    PM->>TDB: Update package.json dependencies
    
    Note over TDB: Version Changes:<br/>workspace:^ → specific versions
    
    TDB->>BC: Update dependency<br/>workspace:^ → 0.24.1
    TDB->>CM: Update dependency<br/>workspace:^ → 0.1.1
    TDB->>CC: Update dependency<br/>workspace:^ → 0.1.0
    TDB->>SM: Update dependency<br/>workspace:^ → 0.4.0
    TDB->>SC: Update dependency<br/>workspace:^ → 0.3.1
    
    Note over TDB,SC: Dependencies now pinned to<br/>specific versions instead of<br/>workspace references
    
    PM-->>TDB: Dependencies resolved

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.

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

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