Skip to content

[Snyk] Security upgrade @backstage/plugin-permission-common from 0.0.0-use.local to 0.1.0#11914

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-f65afa126cd90e187748859af8dc8bf0
Closed

[Snyk] Security upgrade @backstage/plugin-permission-common from 0.0.0-use.local to 0.1.0#11914
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-f65afa126cd90e187748859af8dc8bf0

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 12, 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/jenkins-common/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

This PR updates the dependency version specifier for @backstage/plugin-permission-common in the jenkins-common plugin package configuration.

  • Replaced workspace protocol reference (workspace:^) with fixed version 0.1.0
  • Pins the dependency to a specific version instead of using local workspace version
  • Affects dependency resolution behavior in monorepo environments
  • May indicate preparation for package publishing or version compatibility requirements

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 12, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@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 automates a critical security update to resolve multiple vulnerabilities within the project's dependencies. By upgrading a key Backstage plugin, it enhances the overall security posture and mitigates potential risks associated with outdated packages, ensuring a more robust and secure application environment.

Highlights

  • Security Upgrade: This pull request is an automated security upgrade initiated by Snyk to address 3 identified vulnerabilities.
  • Dependency Update: The @backstage/plugin-permission-common dependency in plugins/jenkins-common/package.json has been upgraded from workspace:^ to version 0.1.0.
  • Vulnerabilities Addressed: The upgrade fixes two Server-side Request Forgery (SSRF) vulnerabilities (SNYK-JS-WEBPACK-15235959, SNYK-JS-WEBPACK-15235969) and one Allocation of Resources Without Limits or Throttling vulnerability (SNYK-JS-QS-15268416).
  • Yarn Lock Warning: A warning is present indicating that the yarn.lock file was not updated and requires manual intervention before merging, especially for projects using Yarn's zero-installs feature.
Changelog
  • plugins/jenkins-common/package.json
    • Updated the version of @backstage/plugin-permission-common to 0.1.0.
Activity
  • The pull request was automatically created by Snyk to address security vulnerabilities.
  • A warning was noted that the yarn.lock file failed to update and requires manual intervention.
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
Copy Markdown

snyk-io Bot commented Feb 12, 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

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

Walkthrough

This pull request modifies the dependency management for the jenkins-common plugin by changing how the @backstage/plugin-permission-common dependency is resolved. The change replaces the workspace protocol reference with a fixed version number, transitioning from dynamic workspace-based resolution to a pinned version. This modification is likely part of package publishing preparation or addressing version compatibility requirements. The change affects dependency resolution behavior, particularly in monorepo environments where workspace protocol is commonly used for local package references.

Changes

File(s) Summary
plugins/jenkins-common/package.json Changed @backstage/plugin-permission-common dependency from workspace protocol (workspace:^) to fixed version (0.1.0), pinning the dependency to a specific version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Jenkins as jenkins-common plugin
    participant PermCommon as plugin-permission-common

    Note over Dev,PermCommon: Dependency Resolution Change

    Dev->>PM: npm install / yarn install
    
    alt Before: workspace:^ version
        PM->>Jenkins: Resolve dependencies
        Jenkins->>PM: Request plugin-permission-common (workspace)
        PM->>PermCommon: Link local workspace version
        PermCommon-->>Jenkins: Local monorepo version
    else After: 0.1.0 version
        PM->>Jenkins: Resolve dependencies
        Jenkins->>PM: Request plugin-permission-common@0.1.0
        PM->>PermCommon: Fetch from npm registry
        PermCommon-->>Jenkins: Published version 0.1.0
    end
    
    PM-->>Dev: Dependencies installed

    Note over Jenkins,PermCommon: No code logic changes<br/>Only dependency source changed
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, aims to address security vulnerabilities by modifying the @backstage/plugin-permission-common dependency. However, the proposed change is incorrect as it downgrades the package from the current workspace version (0.7.7) to a much older, hardcoded version (0.1.0). This breaks the monorepo's dependency strategy of using workspace:^ to ensure all internal packages are consistent. This change will likely lead to build failures or runtime errors and should be rejected. The dependency should continue to reference the workspace version.

"dependencies": {
"@backstage/plugin-catalog-common": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^"
"@backstage/plugin-permission-common": "0.1.0"
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

This change incorrectly downgrades @backstage/plugin-permission-common from the workspace version (which is 0.7.7) to a hardcoded, much older version (0.1.0). In a monorepo using Yarn workspaces, dependencies between packages should use workspace:^ to ensure consistency and use the code from within the repository. Pinning to an old, external version will likely cause build failures or runtime issues and defeats the purpose of a monorepo. This change should be reverted.

Suggested change
"@backstage/plugin-permission-common": "0.1.0"
"@backstage/plugin-permission-common": "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 19, 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