Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 22, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/explore-backend/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 Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  210  
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  146  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  113  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  88  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  88  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  62  

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)
🦉 Prototype Pollution


EntelligenceAI PR Summary

This PR updates dependency versions in the explore-backend plugin to use pinned versions and addresses security vulnerabilities.

  • Pinned @backstage/backend-common to version 0.24.1
  • Pinned @backstage/config to version 0.1.1
  • Pinned @backstage/plugin-search-backend-module-explore to version 0.3.6
  • Pinned @backstage/plugin-search-common to version 0.3.1
  • Upgraded lodash from ^4.17.21 to ^4.17.23 for security fixes
  • Transitioned from workspace protocol references to specific version numbers

@codesandbox
Copy link

codesandbox bot commented Jan 22, 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 addresses critical security concerns by updating several key dependencies within the plugins/explore-backend module. The updates target specific versions of @backstage packages and lodash to mitigate identified vulnerabilities, thereby enhancing the overall security posture of the project.

Highlights

  • Dependency Updates: Several @backstage dependencies have been updated from workspace:^ versions to specific, newer versions (e.g., @backstage/backend-common to 0.24.1, @backstage/config to 0.1.1, @backstage/plugin-search-backend-module-explore to 0.3.6, and @backstage/plugin-search-common to 0.3.1).
  • Security Fixes: The lodash dependency has been updated from ^4.17.21 to ^4.17.23 to address multiple security vulnerabilities, including Prototype Pollution issues.
  • Vulnerability Resolution: This pull request aims to fix a total of 6 vulnerabilities across various dependencies, including a high-severity UNIX Symbolic Link (Symlink) Following vulnerability and several medium-severity issues like Improper Handling of Unicode Encoding, Use of a Cryptographic Primitive with a Risky Implementation, Prototype Pollution, and Regular Expression Denial of Service (ReDoS).
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 22, 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.

@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/@microsoft/api-extractor@7.33.7npm/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

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates dependency management in the explore-backend plugin's package.json. The changes transition four Backstage-scoped dependencies from workspace protocol references to pinned specific versions, ensuring consistent versioning across environments. The @backstage/backend-common is pinned to 0.24.1, @backstage/config to 0.1.1, @backstage/plugin-search-backend-module-explore to 0.3.6, and @backstage/plugin-search-common to 0.3.1. Additionally, the lodash dependency is upgraded from ^4.17.21 to ^4.17.23, which addresses known security vulnerabilities in earlier versions. This update likely prepares the plugin for release or resolves version compatibility requirements.

Changes

File(s) Summary
plugins/explore-backend/package.json Updated four Backstage-scoped dependencies from workspace protocol to pinned versions (@backstage/backend-common: 0.24.1, @backstage/config: 0.1.1, @backstage/plugin-search-backend-module-explore: 0.3.6, @backstage/plugin-search-common: 0.3.1) and upgraded lodash from ^4.17.21 to ^4.17.23.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    
    Note over Dev,Registry: Dependency Update Process (package.json only)
    
    Dev->>PM: Update package.json dependencies
    Note right of Dev: @backstage/backend-common: 0.24.1<br/>@backstage/config: 0.1.1<br/>@backstage/plugin-search-backend-module-explore: 0.3.6<br/>@backstage/plugin-search-common: 0.3.1<br/>lodash: ^4.17.23
    
    Dev->>PM: Run install command
    PM->>Registry: Fetch updated packages
    Registry-->>PM: Return package artifacts
    PM->>PM: Update lock file
    PM-->>Dev: Dependencies updated
    
    Note over Dev,Registry: No runtime interaction changes shown in this PR
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.

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 automated pull request from Snyk attempts to fix vulnerabilities by updating dependencies, but it introduces critical errors. The changes downgrade @backstage/config and @backstage/plugin-search-common to significantly older versions, which will likely break the application. The switch from workspace:^ to pinned versions is also problematic for a monorepo setup. Furthermore, the PR description notes that the yarn.lock file failed to update, which means the fix is incomplete. I recommend rejecting these automated changes and addressing the vulnerabilities manually to avoid breaking the project. The lodash update is correct, but the other changes to @backstage packages are incorrect and should be reverted.

Comment on lines +25 to +29
"@backstage/backend-common": "0.24.1",
"@backstage/config": "0.1.1",
"@backstage/plugin-explore-common": "workspace:^",
"@backstage/plugin-search-backend-module-explore": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-search-backend-module-explore": "0.3.6",
"@backstage/plugin-search-common": "0.3.1",

Choose a reason for hiding this comment

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

critical

These dependency updates have several critical issues:

  1. Major Downgrades: @backstage/config is downgraded from workspace version 1.0.8 to 0.1.1 (line 26), and @backstage/plugin-search-common is downgraded from 1.2.5 to 0.3.1 (line 29). These are massive downgrades that will almost certainly break the application.
  2. Incorrect Dependency Strategy: The change from workspace:^ to pinned versions is problematic in a monorepo. It can lead to version conflicts and bloat. The recommended approach is to either update the workspace packages themselves or use resolutions in the root package.json to fix transitive vulnerabilities without breaking workspace linking.

Given these issues, these changes should be reverted. The lodash update on line 34 is correct, but these changes to @backstage packages are not.

Suggested change
"@backstage/backend-common": "0.24.1",
"@backstage/config": "0.1.1",
"@backstage/plugin-explore-common": "workspace:^",
"@backstage/plugin-search-backend-module-explore": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",
"@backstage/plugin-search-backend-module-explore": "0.3.6",
"@backstage/plugin-search-common": "0.3.1",
"@backstage/backend-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/plugin-explore-common": "workspace:^",
"@backstage/plugin-search-backend-module-explore": "workspace:^",
"@backstage/plugin-search-common": "workspace:^",

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants