[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/gocd/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
	Directory Traversal SNYK-JS-TAR-15127355	127
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	45

---

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:

🦉 Directory Traversal

---

EntelligenceAI PR Summary

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

• Updated @backstage/theme from workspace:^ to 0.1.1 in plugins/gocd/package.json
• Replaces local workspace reference with pinned version
• Ensures consistent theme package version across deployments
• May prevent compatibility issues with theme API changes

[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 performing an automated dependency upgrade. It targets a specific package, @backstage/theme, to mitigate known vulnerabilities, thereby improving the overall security posture of the application. The change is confined to a single dependency version bump, but it necessitates a manual step to ensure full integration.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, upgrades the @backstage/theme dependency from 0.0.0-use.local to 0.1.1 to address two identified vulnerabilities: Directory Traversal (SNYK-JS-TAR-15127355) and Uncontrolled Recursion (SNYK-JS-ESLINT-15102420).
• Dependency Management: The package.json file within the plugins/gocd directory has been updated to reflect the new, more secure version of @backstage/theme.
• Manual Intervention Required: A critical warning indicates that the yarn.lock file failed to update automatically and requires manual intervention to be updated before this pull request can be merged, especially for projects utilizing Yarn's zero-installs feature.

Changelog

• plugins/gocd/package.json
  • Updated the @backstage/theme dependency version from workspace:^ to 0.1.1.

Activity

• This pull request was automatically created by Snyk to fix two identified vulnerabilities.
• Snyk detected a 'Directory Traversal' vulnerability (SNYK-JS-TAR-15127355) with a score of 127.
• Snyk also detected an 'Uncontrolled Recursion' vulnerability (SNYK-JS-ESLINT-15102420) with a score of 45.
• A warning was issued indicating that the yarn.lock file failed to update and requires manual intervention before merging.

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by upgrading @backstage/theme. However, the proposed change from "@backstage/theme": "workspace:^" to "@backstage/theme": "0.1.1" is incorrect for this monorepo setup. It replaces the Yarn workspace protocol with a hardcoded, outdated version, which is likely to cause dependency conflicts and break the build. I've added a comment with a suggestion to revert this change. The Snyk tool seems to have had trouble with the monorepo configuration, as also indicated by the warning about the yarn.lock file.

[gemini-code-assist]

This change incorrectly replaces the workspace:^ protocol with a hardcoded version for @backstage/theme. In a monorepo using Yarn workspaces, workspace:^ ensures that the local package from the workspace is used, promoting consistency. Pinning to a specific, and in this case, much older version (0.1.1) while the workspace version is 0.4.1 will likely lead to build failures, dependency conflicts, or runtime issues. The automated Snyk upgrade appears to have misinterpreted the workspace:^ value. This change should be reverted to maintain the integrity of the monorepo's dependency structure.

Suggested change

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management for the GoCD plugin by changing the @backstage/theme package from a workspace reference to a pinned version. The change moves from using workspace:^ (which references the local monorepo workspace version) to a specific locked version 0.1.1. This modification ensures version stability and predictable behavior by preventing automatic updates to the theme package, which may be necessary for maintaining compatibility with specific theme APIs or avoiding breaking changes during development and deployment.

Changes

File(s)	Summary
plugins/gocd/package.json	Changed @backstage/theme dependency from workspace reference (workspace:^) to pinned version (0.1.1) for version stability.

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

    Note over Dev,GoCD: Dependency Resolution Change

    Dev->>PM: Update package.json<br/>(@backstage/theme: workspace:^ → 0.1.1)
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/theme
        WS-->>PM: Return local workspace version
        PM->>GoCD: Install local theme package
    else After Change (0.1.1)
        PM->>NPM: Fetch @backstage/theme@0.1.1
        NPM-->>PM: Return published version 0.1.1
        PM->>GoCD: Install pinned theme package
    end
    
    Note over GoCD: Plugin now uses<br/>specific theme version 0.1.1

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

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