[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/catalog-graph/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
	Directory Traversal SNYK-JS-TAR-15032660	575

---

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)
🦉 Directory Traversal

---

EntelligenceAI PR Summary

This PR updates the catalog-graph plugin to use fixed versions instead of workspace protocol for core Backstage dependencies.

• Changed @backstage/core-components from workspace protocol to version 0.8.6
• Changed @backstage/core-plugin-api from workspace protocol to version 0.1.0
• Changed @backstage/theme from workspace protocol to version 0.1.1
• Modified in plugins/catalog-graph/package.json

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

[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 polished under OFL-1.1 License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/docs/assets/fonts/LICENSE.txt) From: ? → npm/@storybook/addon-actions@6.5.16 → npm/polished@4.2.2 ℹ 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/polished@4.2.2. 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.
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 catalog-graph plugin by replacing workspace protocol references with fixed version numbers for three core Backstage packages. The changes pin @backstage/core-components to version 0.8.6, @backstage/core-plugin-api to version 0.1.0, and @backstage/theme to version 0.1.1. This modification transitions from using local workspace dependencies to specific published package versions, which typically indicates preparation for independent plugin publication or the need to ensure compatibility with particular versions of these foundational packages.

Changes

File(s)	Summary
plugins/catalog-graph/package.json	Updated dependency resolution strategy from workspace protocol to fixed versions: @backstage/core-components pinned to 0.8.6, @backstage/core-plugin-api to 0.1.0, and @backstage/theme to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant CatalogGraph as catalog-graph Plugin
    participant CoreComponents as @backstage/core-components
    participant CoreAPI as @backstage/core-plugin-api
    participant Theme as @backstage/theme
    
    Note over Build,Theme: Dependency Resolution During Build
    
    Build->>CatalogGraph: Install dependencies
    activate CatalogGraph
    
    CatalogGraph->>CoreComponents: Request version 0.8.6 (pinned)
    activate CoreComponents
    CoreComponents-->>CatalogGraph: Provide fixed version
    deactivate CoreComponents
    
    CatalogGraph->>CoreAPI: Request version 0.1.0 (pinned)
    activate CoreAPI
    CoreAPI-->>CatalogGraph: Provide fixed version
    deactivate CoreAPI
    
    CatalogGraph->>Theme: Request version 0.1.1 (pinned)
    activate Theme
    Theme-->>CatalogGraph: Provide fixed version
    deactivate Theme
    
    CatalogGraph-->>Build: Dependencies resolved with fixed versions
    deactivate CatalogGraph
    
    Note over Build,Theme: Changed from workspace:^ to specific versions<br/>for core-components, core-plugin-api, and theme

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!