[Snyk] Security upgrade @backstage/plugin-search-react from 0.0.0-use.local to 0.1.0

[q1blue]

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

Snyk changed the following file(s):

• plugins/adr/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

Updated dependency version for '@backstage/plugin-search-react' in the ADR plugin to use a fixed version instead of workspace reference.

• Changed dependency from 'workspace:^' to '0.1.0' in plugins/adr/package.json
• Pins the plugin to a specific published version rather than using local workspace version
• May indicate transition to published package or resolution of version compatibility issues

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

[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 automates a critical security update for the @backstage/plugin-search-react dependency within the plugins/adr package. The primary goal is to mitigate known vulnerabilities, specifically Directory Traversal and Uncontrolled Recursion, by upgrading the package version. This ensures the project maintains a secure dependency chain against identified threats.

Highlights

• Security Upgrade: Upgraded the @backstage/plugin-search-react dependency from workspace:^ (effectively 0.0.0-use.local) to 0.1.0 in plugins/adr/package.json.
• Vulnerability Fixes: This upgrade addresses two medium-severity vulnerabilities: Directory Traversal (SNYK-JS-TAR-15127355) and Uncontrolled Recursion (SNYK-JS-ESLINT-15102420).
• Automated PR: This pull request was automatically generated by Snyk to apply the necessary security fixes.
• Yarn Zero-Installs Note: Users of Yarn's zero-installs feature will need to manually run yarn to update the .yarn/cache/ directory, as this PR does not update it automatically.

Changelog

• plugins/adr/package.json
  • Upgraded the @backstage/plugin-search-react dependency from workspace:^ to 0.1.0.

Activity

• This pull request was automatically created by Snyk to address identified security vulnerabilities.
• The PR description includes a warning about a failed yarn.lock update, suggesting manual intervention might be required.
• Snyk has provided links to detailed vulnerability reports and learning resources for the identified issues.

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

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the ADR plugin by changing the '@backstage/plugin-search-react' dependency from a workspace protocol reference to a fixed version. The change pins the dependency to version 0.1.0 instead of using the dynamic workspace reference (workspace:^). This modification likely indicates a transition from local development dependencies to using a published package version, or addresses version compatibility issues by ensuring a specific version is used rather than relying on the workspace's version resolution.

Changes

File(s)	Summary
plugins/adr/package.json	Changed '@backstage/plugin-search-react' dependency from workspace protocol reference ('workspace:^') to fixed version '0.1.0'.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace Registry
    participant NPM as NPM Registry
    
    Note over Dev,NPM: Dependency Resolution Change
    
    Dev->>PM: Install dependencies (before change)
    PM->>WS: Resolve @backstage/plugin-search-react@workspace:^
    WS-->>PM: Return local workspace package
    PM-->>Dev: Dependencies installed (local version)
    
    Note over Dev,NPM: After PR Change
    
    Dev->>PM: Install dependencies (after change)
    PM->>NPM: Resolve @backstage/plugin-search-react@0.1.0
    NPM-->>PM: Return published package v0.1.0
    PM-->>Dev: Dependencies installed (published version)
    
    Note over Dev,NPM: Runtime behavior remains unchanged

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 aims to address security vulnerabilities by upgrading @backstage/plugin-search-react. However, the proposed change in plugins/adr/package.json appears to be a significant downgrade of the @backstage/plugin-search-react dependency from a "workspace:^" version (which typically resolves to 1.x.x in the current workspace) to "0.1.0". This is contrary to the "upgrade" stated in the PR title and description and is highly likely to introduce breaking changes or compatibility issues. Furthermore, the pull request description indicates that the yarn.lock file was not updated, which means the PR is incomplete and requires manual intervention to ensure all dependencies are correctly resolved and the security fix is properly applied.

[gemini-code-assist]

The change from "@backstage/plugin-search-react": "workspace:^" to "@backstage/plugin-search-react": "0.1.0" appears to be a significant downgrade. The "workspace:^" typically resolves to the latest version within the monorepo, which for @backstage/plugin-search-react is currently 1.6.4-next.0 (as seen in plugins/search-react/package.json). Downgrading to 0.1.0 is likely to introduce breaking changes and is inconsistent with the "Security upgrade" stated in the PR title. Please verify if 0.1.0 is indeed the correct target version for this security fix, or if a newer, compatible version should be used.