Skip to content

[Snyk] Fix for 3 vulnerabilities#12036

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-9173a693cd44a62f58eaf70cdcb510fa
Closed

[Snyk] Fix for 3 vulnerabilities#12036
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-9173a693cd44a62f58eaf70cdcb510fa

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 13, 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/entity-validation/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
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  83  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  83  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

Updated dependency version constraints in the entity-validation plugin to use fixed versions instead of workspace protocol.

  • Changed @backstage/plugin-catalog-react from workspace:^ to 0.0.1
  • Changed @backstage/theme from workspace:^ to 0.1.1
  • Transitions from monorepo workspace resolution to explicit version pinning
  • May indicate preparation for independent plugin publishing or version compatibility requirements

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 13, 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
Copy Markdown

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 argparse under Python-2.0.1

License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/js-yaml@4.1.0npm/argparse@2.0.1

ℹ 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/argparse@2.0.1. 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.

Warn High
License policy violation: npm caniuse-lite under CC-BY-4.0

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata)

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

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

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/caniuse-lite@1.0.30001481

ℹ 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/caniuse-lite@1.0.30001481. 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.

Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/entities@4.4.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. 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.

Warn High
Obfuscated code: npm html-minifier-terser is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ?npm/@docusaurus/core@0.0.0-5591npm/html-minifier-terser@7.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

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: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/html-minifier-terser@7.2.0. 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

@gemini-code-assist
Copy link
Copy Markdown

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 three vulnerabilities within the project's yarn dependencies by updating specific package versions. It includes a note for users of Yarn's zero-installs feature and a warning about a failed yarn.lock update.

Highlights

  • Dependency Updates: This PR updates the versions of @backstage/plugin-catalog-react and @backstage/theme in the plugins/entity-validation/package.json file.
  • Vulnerability Fixes: The primary goal of this PR is to address and fix three identified vulnerabilities in the project's yarn dependencies, as reported by Snyk.
  • Yarn Zero-Installs Note: The PR description includes a note for users utilizing Yarn's zero-installs feature, advising them to update the .yarn/cache/ directory manually after merging.
  • Failed yarn.lock Update: The PR description warns that the yarn.lock file failed to update automatically and requires manual updating before merging.
Changelog
  • plugins/entity-validation/package.json
    • Updated @backstage/plugin-catalog-react from workspace:^ to 0.0.1.
    • Updated @backstage/theme from workspace:^ to 0.1.1.
Activity
  • Snyk automatically opened this PR to address vulnerabilities.
  • The PR updates dependencies in plugins/entity-validation/package.json.
  • The PR description warns about a failed yarn.lock update.
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.

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR modifies the dependency management strategy for the entity-validation plugin by replacing workspace protocol references with fixed version numbers. Specifically, two Backstage dependencies (@backstage/plugin-catalog-react and @backstage/theme) are pinned to versions 0.0.1 and 0.1.1 respectively, moving away from the monorepo workspace resolution pattern (workspace:^). This change likely prepares the plugin for independent distribution or addresses specific version compatibility requirements that necessitate explicit version pinning rather than dynamic workspace resolution.

Changes

File(s) Summary
plugins/entity-validation/package.json Replaced workspace protocol (workspace:^) with fixed versions for two dependencies: @backstage/plugin-catalog-react pinned to 0.0.1 and @backstage/theme pinned to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant EntityValidation as Entity Validation Plugin
    participant CatalogReact as @backstage/plugin-catalog-react
    participant Theme as @backstage/theme
    
    Note over Build,Theme: Dependency Resolution Change
    
    Build->>EntityValidation: Resolve dependencies
    
    alt Before Change (workspace reference)
        EntityValidation->>CatalogReact: Request workspace:^ version
        CatalogReact-->>EntityValidation: Return local workspace version
        EntityValidation->>Theme: Request workspace:^ version
        Theme-->>EntityValidation: Return local workspace version
    else After Change (pinned versions)
        EntityValidation->>CatalogReact: Request version 0.0.1
        CatalogReact-->>EntityValidation: Return pinned version 0.0.1
        EntityValidation->>Theme: Request version 0.1.1
        Theme-->>EntityValidation: Return pinned version 0.1.1
    end
    
    EntityValidation-->>Build: Dependencies resolved
    
    Note over EntityValidation: Plugin now uses specific<br/>versions instead of workspace refs
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
Copy Markdown

@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 three vulnerabilities by updating dependencies. However, the proposed changes in plugins/entity-validation/package.json are incorrect. It replaces workspace-linked packages (workspace:^) with very old, pinned versions from the public registry. This will almost certainly break the application, so I have left a critical comment with a suggestion to revert the change. The underlying vulnerabilities need to be addressed in a way that respects the monorepo's structure, likely by updating the workspace packages or their transitive dependencies.

Comment on lines +36 to +37
"@backstage/plugin-catalog-react": "0.0.1",
"@backstage/theme": "0.1.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

These changes, intended to fix vulnerabilities, are incorrect and will likely break the project. They replace workspace:^ dependencies with very old, pinned versions of @backstage/plugin-catalog-react and @backstage/theme, breaking the monorepo workspace linking.

  • @backstage/plugin-catalog-react is being downgraded from a workspace version (the current version in the workspace is 1.8.1-next.0) to 0.0.1.
  • @backstage/theme is being downgraded from a workspace version (the current version in the workspace is 0.4.1) to 0.1.1.

These changes should be reverted. The vulnerabilities need to be addressed in a way that is compatible with the project's monorepo structure, for example by updating the packages within the workspace.

Suggested change
"@backstage/plugin-catalog-react": "0.0.1",
"@backstage/theme": "0.1.1",
"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/theme": "workspace:^",

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Mar 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants