[Snyk] Fix for 1 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/kubernetes-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-OCTOKITREQUESTERROR-8730854	67

---

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)

Summary by Sourcery

Update dependencies to fix a Snyk vulnerability in the Kubernetes backend plugin

Bug Fixes:

• Fix a Regular Expression Denial of Service (ReDoS) vulnerability in dependencies

Enhancements:

• Update @backstage/catalog-model from workspace to version 0.1.1
• Update @backstage/plugin-catalog-node from workspace to version 1.0.0

---

EntelligenceAI PR Summary

This PR pins Backstage dependencies to specific versions in the kubernetes-backend plugin, replacing workspace protocol references.

• Changed @backstage/catalog-model from workspace:^ to fixed version 0.1.1
• Changed @backstage/plugin-catalog-node from workspace:^ to fixed version 1.0.0
• Transitions from local workspace resolution to published package versions
• Modified in plugins/kubernetes-backend/package.json

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[sourcery-ai]

Reviewer's Guide

This pull request, automatically generated by Snyk, updates two dependency versions in package.json to remediate a reported vulnerability.

File-Level Changes

Change	Details	Files
Bumped dependency versions to fix a Snyk vulnerability.	Updated @backstage/catalog-model from workspace:^ to 0.1.1. Updated @backstage/plugin-catalog-node from workspace:^ to 1.0.0.	plugins/kubernetes-backend/package.json
Manual action required.	The yarn.lock file needs to be updated manually before merging, as noted in the PR description.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

⛔ Snyk checks have failed. 80 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (80)
⛔	Open Source Security	15	24	36	5	80 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!

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​rjsf/​material-ui-v5@​5.7.3

View full report

[socket-security]

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

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

[entelligence-ai-pr-reviews]

🔒 Entelligence AI Vulnerability Scanner

✅ No security vulnerabilities found!

Your code passed our comprehensive security analysis.

---

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates dependency management in the kubernetes-backend plugin by replacing workspace protocol references with fixed version specifications. Two Backstage dependencies are now pinned to specific versions: @backstage/catalog-model at version 0.1.1 and @backstage/plugin-catalog-node at version 1.0.0. This change transitions from local workspace resolution to published package versions, likely in preparation for plugin publication or to address version compatibility requirements in the deployment pipeline.

Changes

File(s)	Summary
plugins/kubernetes-backend/package.json	Updated two dependencies from workspace protocol (workspace:^) to fixed versions: @backstage/catalog-model pinned to 0.1.1 and @backstage/plugin-catalog-node pinned to 1.0.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as package.json
    participant PM as Package Manager
    participant Deps as Dependencies

    Note over Dev,Deps: Dependency Version Pinning Process

    Dev->>PKG: Update @backstage/catalog-model<br/>workspace:^ → 0.1.1
    Dev->>PKG: Update @backstage/plugin-catalog-node<br/>workspace:^ → 1.0.0
    
    Note over PKG: Configuration changes only<br/>No runtime behavior modified

    Dev->>PM: Run package install
    PM->>Deps: Resolve @backstage/catalog-model@0.1.1
    Deps-->>PM: Return fixed version
    PM->>Deps: Resolve @backstage/plugin-catalog-node@1.0.0
    Deps-->>PM: Return fixed version
    
    PM-->>Dev: Dependencies locked to specific versions

    Note over Dev,Deps: kubernetes-backend plugin now uses<br/>pinned versions 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!