[Snyk] Security upgrade @backstage/theme from 0.0.0-use.local to 0.1.1

[q1blue]

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

Snyk changed the following file(s):

• plugins/shortcuts/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
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	84
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	84

---

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:

🦉 Server-side Request Forgery (SSRF)

---

EntelligenceAI PR Summary

This PR pins the @backstage/theme dependency to a specific version in the shortcuts plugin for improved version stability.

• Updated @backstage/theme dependency from workspace:^ to 0.1.1 in plugins/shortcuts/package.json
• Replaces local workspace version reference with fixed version pinning
• Affects dependency resolution and package distribution for the shortcuts plugin
• Ensures compatibility with specific theme API version

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's security by upgrading a critical dependency. It specifically targets and resolves two Server-side Request Forgery vulnerabilities, ensuring the application is protected against these known exploits. The change is confined to a single package manifest file, reflecting a precise and targeted security patch.

Highlights

• Dependency Upgrade: The @backstage/theme dependency has been upgraded from workspace:^ to version 0.1.1 in plugins/shortcuts/package.json.
• Security Fixes: This upgrade addresses two Server-side Request Forgery (SSRF) vulnerabilities, identified as SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969, both with a severity score of 84.
• Automated PR: This pull request was automatically generated by Snyk to apply the necessary security updates.

Changelog

• plugins/shortcuts/package.json
  • Updated the @backstage/theme dependency version from workspace:^ to 0.1.1 to incorporate security fixes.

Activity

• This pull request was automatically created by Snyk to remediate identified vulnerabilities.
• Snyk reported that the yarn.lock file failed to update and requires manual intervention before merging.
• Guidance was provided for users of Yarn's zero-install feature, advising to run yarn to update the .yarn/cache/ directory.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 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 for the shortcuts plugin by changing the @backstage/theme package reference from a workspace protocol to a fixed version. The change moves from using workspace:^ (which references the local workspace version) to pinning the dependency at version 0.1.1. This modification ensures version stability and predictable behavior for the theme package dependency, which may be necessary for compatibility requirements or to avoid potential breaking changes from workspace updates. The change affects how the shortcuts plugin resolves and bundles its dependencies during build and distribution processes.

Changes

File(s)	Summary
plugins/shortcuts/package.json	Changed @backstage/theme dependency from workspace protocol reference (workspace:^) to fixed version 0.1.1 to pin the theme package version.

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 Plugin as Shortcuts Plugin

    Dev->>PM: Install dependencies
    PM->>Plugin: Read package.json
    
    Note over Plugin,NPM: Before: workspace:^ reference
    alt Old Behavior (workspace:^)
        PM->>WS: Resolve @backstage/theme from workspace
        WS-->>PM: Return local workspace version
    else New Behavior (0.1.1)
        PM->>NPM: Fetch @backstage/theme@0.1.1
        NPM-->>PM: Return version 0.1.1
    end
    
    PM->>Plugin: Install resolved dependency
    Plugin-->>Dev: Dependencies installed

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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to resolve security vulnerabilities by upgrading the @backstage/theme package. However, the proposed change of pinning @backstage/theme to version 0.1.1 in plugins/shortcuts/package.json is not appropriate for this monorepo structure. It replaces the workspace:^ reference, which links to the local @backstage/theme package, with a fixed version from the public registry. This will likely cause dependency conflicts, bundle size increases, and inconsistencies, as the monorepo contains a newer version (0.4.1). The correct approach is to address the vulnerability within the @backstage/theme package itself or its dependencies at the monorepo level, while preserving the workspace linking.

[gemini-code-assist]

Pinning the @backstage/theme dependency to a specific version (0.1.1) breaks the monorepo's workspace linking. This package should reference the local @backstage/theme package using workspace:^ to ensure consistency and use the code from within this repository. The current version of @backstage/theme in the workspace is 0.4.1, so this change would also introduce an outdated version. The security vulnerability should be addressed within the @backstage/theme package at the root of the monorepo, not by pinning a version in a consuming package.

Suggested change

	"@backstage/theme": "0.1.1",
	"@backstage/theme": "workspace:^",

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