Skip to content

[Snyk] Security upgrade @apollo/server from 4.8.1 to 5.4.0#11674

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-3ea719317e900d68ff0493a6ca480d14
Open

[Snyk] Security upgrade @apollo/server from 4.8.1 to 5.4.0#11674
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-3ea719317e900d68ff0493a6ca480d14

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Feb 6, 2026

snyk-top-banner

Snyk has created this PR to fix 1 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
  635  

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)


EntelligenceAI PR Summary

This PR upgrades Apollo Server from v4 to v5.4.0 in the catalog-graphql plugin.

  • Updated @apollo/server dependency from ^4.0.0 to ^5.4.0 in plugins/catalog-graphql/package.json
  • Major version upgrade may include breaking changes requiring code adjustments
  • Brings performance improvements and new features from Apollo Server v5

@codesandbox
Copy link

codesandbox bot commented Feb 6, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Author

snyk-io bot commented Feb 6, 2026

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
Copy link

Walkthrough

This pull request upgrades the Apollo Server dependency in the catalog-graphql plugin from version 4.x to version 5.4.0, representing a major version update. Apollo Server v5 introduces breaking changes and new features that may require code adjustments to maintain compatibility. This upgrade affects the GraphQL server implementation within the catalog-graphql plugin and should be accompanied by corresponding code changes to align with the new API surface. The update brings potential performance improvements and access to the latest features available in Apollo Server v5.

Changes

File(s) Summary
plugins/catalog-graphql/package.json Upgraded @apollo/server dependency from version ^4.0.0 to ^5.4.0, a major version update that may include breaking changes and new features.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Client
    participant CatalogGraphQL as Catalog GraphQL Plugin
    participant ApolloServer as Apollo Server (v4→v5)
    participant CatalogModel as Catalog Model
    participant Backend as Backstage Backend

    Note over ApolloServer: Upgraded from v4.0.0 to v5.4.0

    Client->>CatalogGraphQL: GraphQL Query Request
    activate CatalogGraphQL
    
    CatalogGraphQL->>ApolloServer: Parse & Validate Query
    activate ApolloServer
    
    ApolloServer->>CatalogGraphQL: Validated Query
    deactivate ApolloServer
    
    CatalogGraphQL->>CatalogModel: Resolve Entity Data
    activate CatalogModel
    
    CatalogModel->>Backend: Fetch Catalog Entities
    activate Backend
    
    Backend-->>CatalogModel: Entity Data
    deactivate Backend
    
    CatalogModel-->>CatalogGraphQL: Resolved Data
    deactivate CatalogModel
    
    CatalogGraphQL->>ApolloServer: Format Response
    activate ApolloServer
    
    ApolloServer-->>CatalogGraphQL: GraphQL Response
    deactivate ApolloServer
    
    CatalogGraphQL-->>Client: Query Result
    deactivate CatalogGraphQL
    
    Note over Client,Backend: Apollo Server v5 may include<br/>performance improvements and<br/>updated GraphQL execution
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.

@socket-security
Copy link

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/typescript@4.8.4

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/typescript@4.8.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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.

0 participants