Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 31, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/techdocs-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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  61  
medium severity 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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal


EntelligenceAI PR Summary

This PR updates dependency resolution in the techdocs-react plugin from workspace protocol to fixed package versions.

  • Changed @backstage/core-components from workspace:^ to fixed version 0.8.6
  • Changed @backstage/core-plugin-api from workspace:^ to fixed version 0.1.0
  • Shifts from monorepo workspace dependencies to published package versions
  • Modified in plugins/techdocs-react/package.json

@codesandbox
Copy link

codesandbox bot commented Jan 31, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! 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, automatically generated by Snyk, aims to enhance the project's security posture by resolving four identified medium-severity vulnerabilities within the plugins/techdocs-react package's yarn dependencies. The changes involve specific version upgrades for @backstage/core-components and @backstage/core-plugin-api to mitigate these risks.

Highlights

  • Dependency Updates: Updated @backstage/core-components from workspace:^ to 0.8.6 and @backstage/core-plugin-api from workspace:^ to 0.1.0 in plugins/techdocs-react/package.json.
  • Vulnerability Fixes: This PR addresses 4 medium-severity vulnerabilities, including Directory Traversal, Regular Expression Denial of Service (ReDoS), and Uncontrolled Recursion, as identified by Snyk.
  • Yarn Zero-Installs Note: Users of Yarn's zero-installs feature will need to run yarn to update the .yarn/cache/ directory, as this PR does not update it automatically.
  • yarn.lock Warning: 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.

@snyk-io
Copy link

snyk-io bot commented Jan 31, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, attempts to fix four security vulnerabilities by updating dependencies. However, the proposed changes are incorrect and introduce critical issues. It replaces internal workspace dependencies (workspace:^) with very old, pinned versions from the public registry for @backstage/core-components and @backstage/core-plugin-api. This constitutes a major downgrade and will likely break the build process and the application's functionality. The changes should be reverted, and the vulnerabilities should be addressed by updating the correct packages within the monorepo structure.

Comment on lines +38 to +39
"@backstage/core-components": "0.8.6",
"@backstage/core-plugin-api": "0.1.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

These changes incorrectly replace workspace-local dependencies (workspace:^) with old, pinned versions from the public registry. This is a significant downgrade and will likely break the application. @backstage/core-components is being downgraded from a workspace version (which is 0.13.4-next.0 in this monorepo) to 0.8.6, and @backstage/core-plugin-api from a workspace version (1.5.3) to 0.1.0.

This change should be reverted. To fix the underlying vulnerabilities, the dependencies within the monorepo should be updated, not by pinning to old versions from an external registry.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^"

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR modifies the dependency resolution strategy for the techdocs-react plugin by replacing workspace protocol references with fixed package versions. The change affects two core Backstage dependencies: @backstage/core-components is now pinned to version 0.8.6 and @backstage/core-plugin-api to version 0.1.0. Previously, these dependencies used the workspace:^ protocol to resolve to local monorepo packages. This transition from workspace-based to published package versions represents a shift in dependency management approach, which may impact version compatibility, build processes, and package distribution strategies across the project.

Changes

File(s) Summary
plugins/techdocs-react/package.json Replaced workspace protocol (workspace:^) with fixed versions for @backstage/core-components (pinned to 0.8.6) and @backstage/core-plugin-api (pinned to 0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant Package as techdocs-react
    participant CoreComp as @backstage/core-components
    participant CoreAPI as @backstage/core-plugin-api
    
    Note over Build,CoreAPI: Dependency Resolution Change
    
    Build->>Package: Resolve dependencies
    
    alt Before Change (workspace:^)
    Package->>CoreComp: Request workspace version
    CoreComp-->>Package: Return local workspace version
    Package->>CoreAPI: Request workspace version
    CoreAPI-->>Package: Return local workspace version
    else After Change (pinned versions)
    Package->>CoreComp: Request version 0.8.6
    CoreComp-->>Package: Return specific version 0.8.6
    Package->>CoreAPI: Request version 0.1.0
    CoreAPI-->>Package: Return specific version 0.1.0
    end
    
    Package-->>Build: Dependencies resolved
    
    Note over Package,CoreAPI: Pinned versions ensure<br/>consistent builds across environments
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants