Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Feb 9, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/catalog-graphql/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
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-APOLLOSERVER-15208673
  167  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  84  
low severity 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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

Updates dependencies in the catalog-graphql plugin to newer versions with more explicit version control.

  • Upgraded @apollo/server from ^4.0.0 to ^5.4.0 (major version change)
  • Changed @backstage/types from workspace protocol to fixed version 0.1.1
  • Major Apollo Server upgrade may include breaking changes and new v5 features

@codesandbox
Copy link

codesandbox bot commented Feb 9, 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, focuses on improving the project's security by upgrading specific dependencies within the plugins/catalog-graphql module. The updates are crucial for mitigating three identified vulnerabilities, including a high-severity ReDoS and two low-severity SSRF issues, thereby enhancing the overall robustness and safety of the application.

Highlights

  • Dependency Upgrades: The @apollo/server package has been updated from ^4.0.0 to ^5.4.0, and @backstage/types from workspace:^ to 0.1.1 in plugins/catalog-graphql/package.json.
  • Vulnerability Resolution: This PR addresses three security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-APOLLOSERVER-15208673) and two low-severity Server-side Request Forgery (SSRF) issues (SNYK-JS-WEBPACK-15235959, SNYK-JS-WEBPACK-15235969).
  • Manual yarn.lock Update Required: A warning indicates that the yarn.lock file was not automatically updated and requires manual intervention before merging.
Changelog
  • plugins/catalog-graphql/package.json
    • The @apollo/server dependency has been upgraded from version ^4.0.0 to ^5.4.0.
    • The @backstage/types dependency has been updated from workspace:^ to 0.1.1.
Activity
  • This pull request was automatically created by Snyk to provide fixes for identified security vulnerabilities.
  • Snyk reported that the yarn.lock file could not be updated automatically, indicating a necessary manual step for completion.
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.

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, addresses three security vulnerabilities by upgrading dependencies. The upgrade of @apollo/server to a new major version (^5.4.0) is necessary to patch a high-severity ReDoS vulnerability. However, the change to @backstage/types appears to be an error. It incorrectly downgrades the package to version 0.1.1 and breaks the monorepo's workspace convention by removing workspace:^. This critical issue, detailed in my comment, needs to be fixed before merging. After correcting the @backstage/types dependency, you will need to manually run yarn to update the yarn.lock file, as noted in the pull request description.

"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",

Choose a reason for hiding this comment

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

critical

This automated change incorrectly modifies the version of @backstage/types. It changes from workspace:^ to a hardcoded, older version 0.1.1. This is problematic for several reasons:

  1. Breaks Monorepo Dependency Management: It deviates from the established pattern of using workspace:^ for packages within this monorepo, which can lead to an inconsistent dependency graph.
  2. Significant Downgrade: This is a major downgrade from the workspace version (which is 1.1.0 according to the repository files), likely introducing type incompatibilities and build failures, especially since other packages like @backstage/catalog-model rely on the workspace version.
  3. Automated Tool Error: This change appears to be an error by the Snyk automation, which is also suggested by the warning in the PR description: Failed to update the yarn.lock, please update manually before merging.

This dependency should be reverted to workspace:^ to maintain consistency and correctness within the monorepo.

Suggested change
"@backstage/types": "0.1.1",
"@backstage/types": "workspace:^",

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates dependencies for the catalog-graphql plugin, focusing on two key changes. The Apollo Server package is upgraded from version 4.x to 5.4.0, representing a major version bump that may introduce breaking changes and new features from the v5 release line. Additionally, the @backstage/types dependency is changed from using the workspace protocol to a pinned external version 0.1.1, ensuring a fixed version rather than a workspace-relative dependency. These changes modernize the plugin's dependencies and establish more explicit version control.

Changes

File(s) Summary
plugins/catalog-graphql/package.json Upgraded @apollo/server from ^4.0.0 to ^5.4.0 (major version bump) and changed @backstage/types from workspace protocol to pinned version 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client as GraphQL Client
    participant Plugin as Catalog GraphQL Plugin
    participant Apollo as Apollo Server (v5.4.0)
    participant Modules as GraphQL Modules
    participant Catalog as Backstage Catalog Model
    participant Config as Backstage Config
    
    Note over Apollo: Upgraded from v4 to v5.4.0
    Note over Plugin: Uses @backstage/types v0.1.1
    
    Client->>Plugin: GraphQL Query Request
    activate Plugin
    
    Plugin->>Apollo: Initialize Server
    activate Apollo
    Apollo-->>Plugin: Server Ready
    deactivate Apollo
    
    Plugin->>Modules: Load GraphQL Schema
    activate Modules
    Modules-->>Plugin: Schema Loaded
    deactivate Modules
    
    Plugin->>Apollo: Execute Query
    activate Apollo
    
    Apollo->>Catalog: Fetch Catalog Data
    activate Catalog
    Catalog->>Config: Get Configuration
    activate Config
    Config-->>Catalog: Config Values
    deactivate Config
    Catalog-->>Apollo: Catalog Entities
    deactivate Catalog
    
    Apollo-->>Plugin: Query Result
    deactivate Apollo
    
    Plugin-->>Client: GraphQL Response
    deactivate Plugin
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
Copy link

snyk-io bot commented Feb 9, 2026

⚠️ Snyk checks are incomplete.

Status Scanner Critical High Medium Low Total (0)
⚠️ Open Source Security 0 0 0 0 See details

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

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.

2 participants