[Snyk] Security upgrade @backstage/types 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/search-react/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 pins the @backstage/types dependency to version 0.1.1 in the search-react plugin for improved stability and compatibility.

• Replaced workspace protocol reference (workspace:^) with fixed version (0.1.1)
• Modified dependency declaration in plugins/search-react/package.json
• Ensures consistent type definitions by using a specific published version instead of local workspace 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 automates a critical security update for a core dependency, enhancing the project's overall security posture by resolving known vulnerabilities. The change involves a targeted package version bump to mitigate potential risks without introducing broader functional modifications.

Highlights

• Dependency Upgrade: The @backstage/types dependency has been upgraded from 0.0.0-use.local to 0.1.1 in plugins/search-react/package.json.
• Security Fixes: This upgrade addresses two identified vulnerabilities: a Directory Traversal issue (SNYK-JS-TAR-15127355) and an Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
• Automated PR: This pull request was automatically generated by Snyk to apply the necessary security fixes.

Changelog

• plugins/search-react/package.json
  • Updated the @backstage/types dependency version from workspace:^ (effectively 0.0.0-use.local) to 0.1.1.

Activity

• This pull request was automatically created by Snyk to fix two identified vulnerabilities in the project's yarn dependencies.
• Snyk reported a failure to update the yarn.lock file, indicating that manual intervention will be required to complete the dependency update process.
• The PR description includes detailed information about the vulnerabilities being fixed, including their severity scores and links to Snyk's vulnerability database and learning resources.

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 search-react plugin by pinning the @backstage/types package to a specific version. The change moves from using a workspace protocol reference (which points to the local monorepo version) to a fixed published version 0.1.1. This modification ensures the plugin uses a stable, published version of the types package rather than relying on the workspace version, which may be necessary for compatibility requirements or to ensure consistent type definitions across different environments.

Changes

File(s)	Summary
plugins/search-react/package.json	Changed @backstage/types dependency from workspace protocol reference (workspace:^) to fixed version 0.1.1 to pin the package to a specific published version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant SR as search-react Plugin
    participant WS as Workspace
    participant NPM as NPM Registry

    Note over PM,NPM: Dependency Resolution Change

    PM->>SR: Read package.json
    SR-->>PM: Dependencies list
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/types
        WS-->>PM: Local workspace version
    else After Change (0.1.1)
        PM->>NPM: Fetch @backstage/types@0.1.1
        NPM-->>PM: Package version 0.1.1
    end
    
    PM->>SR: Install resolved dependency
    Note over SR: search-react now uses<br/>@backstage/types@0.1.1<br/>from NPM registry

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 fix security vulnerabilities by upgrading the @backstage/types dependency. However, the proposed change from workspace:^ to a pinned version 0.1.1 is incorrect for this monorepo setup. It constitutes a significant downgrade from the local version (1.1.0) and breaks the workspace integrity, which will likely cause build failures. I have left a critical comment suggesting to revert this change. The security vulnerabilities should be addressed by updating the dependencies within the @backstage/types package itself.

[gemini-code-assist]

This automated change incorrectly replaces the monorepo workspace:^ protocol with a pinned version from the npm registry. This is a significant issue for several reasons:

1. Breaks Monorepo Integrity: It decouples this package from the local @backstage/types package, defeating the purpose of the monorepo setup. Changes made to @backstage/types locally will no longer be picked up.
2. Significant Downgrade: The version is pinned to 0.1.1, while the version of @backstage/types within this monorepo is 1.1.0 (as seen in packages/types/package.json). This is a major downgrade and will almost certainly lead to compilation errors or runtime issues due to API incompatibilities.
3. Incorrect Fix Strategy: The underlying security vulnerabilities should be addressed by updating the dependencies of the @backstage/types package itself, not by pinning a dependent package to an old, arbitrary version.

This change should be reverted to maintain the integrity of the workspace. The security vulnerabilities need to be addressed at their source.

    "@backstage/types": "workspace:^"