[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/jenkins/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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157
	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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR transitions the Jenkins plugin from workspace protocol dependencies to explicit version pinning for Backstage packages.

• Changed @backstage/catalog-model from workspace protocol to version 0.1.1
• Changed @backstage/plugin-catalog-react from workspace protocol to version 0.0.1
• Changed @backstage/plugin-jenkins-common from workspace protocol to version 0.1.0
• Modifications made in plugins/jenkins/package.json
• Enables standalone package distribution and explicit dependency management

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! 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, aims to enhance the security posture of the project by resolving two identified vulnerabilities. It achieves this by upgrading several @backstage dependencies within the plugins/jenkins module, specifically targeting issues related to Regular Expression Denial of Service and resource allocation.

Highlights

• Vulnerability Fixes: Addressed two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416).
• Dependency Upgrades: Upgraded @backstage/catalog-model to 0.1.1, @backstage/plugin-catalog-react to 0.0.1, and @backstage/plugin-jenkins-common to 0.1.0 in plugins/jenkins/package.json to resolve the identified vulnerabilities.

Changelog

• plugins/jenkins/package.json
  • Updated @backstage/catalog-model from workspace:^ to 0.1.1.
  • Updated @backstage/plugin-catalog-react from workspace:^ to 0.0.1.
  • Updated @backstage/plugin-jenkins-common from workspace:^ to 0.1.0.

Activity

• The pull request was automatically created by Snyk to fix identified vulnerabilities.
• A warning was noted indicating that yarn.lock 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]

⛔ Snyk checks have failed. 1 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	0	1	0	1 issues

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix two vulnerabilities. However, the proposed dependency changes are incorrect. It downgrades several @backstage packages to very old versions and removes the workspace: protocol, which is a standard practice in this monorepo. These changes will likely break the build and should be reverted. This seems to be caused by a misconfiguration in the Snyk scanner not handling yarn workspaces correctly. The vulnerabilities should be addressed differently, likely by updating workspace packages and the lockfile.

[gemini-code-assist]

The proposed dependency changes are incorrect. They replace workspace:^ with very old, pinned versions of Backstage packages, which is a significant downgrade and deviates from the monorepo's dependency management strategy. For example, @backstage/catalog-model is at version 1.4.1 in the workspace, but this change pins it to 0.1.1. This will likely cause build failures and other issues. This is probably due to a Snyk misconfiguration with yarn workspaces. The changes should be reverted.

    "@backstage/catalog-model": "workspace:^",
    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/errors": "workspace:^",
    "@backstage/plugin-catalog-react": "workspace:^",
    "@backstage/plugin-jenkins-common": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the Jenkins plugin's dependency management by transitioning from workspace protocol references to explicit version pinning for three Backstage packages. The changes affect the package.json file, replacing workspace dependencies with fixed versions: @backstage/catalog-model (0.1.1), @backstage/plugin-catalog-react (0.0.1), and @backstage/plugin-jenkins-common (0.1.0). This modification is likely part of preparing the Jenkins plugin for standalone distribution or improving dependency resolution in the build process by explicitly declaring version requirements rather than relying on monorepo workspace resolution.

Changes

File(s)	Summary
plugins/jenkins/package.json	Updated three Backstage package dependencies from workspace protocol to fixed versions: @backstage/catalog-model to 0.1.1, @backstage/plugin-catalog-react to 0.0.1, and @backstage/plugin-jenkins-common to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Jenkins as Jenkins Plugin
    participant CM as @backstage/catalog-model
    participant PCR as @backstage/plugin-catalog-react
    participant PJC as @backstage/plugin-jenkins-common

    Note over Dev,PJC: Dependency Version Update Process

    Dev->>PM: Update package.json dependencies
    Note over PM: Change workspace references<br/>to specific versions

    PM->>Jenkins: Resolve dependencies
    
    Jenkins->>CM: Request v0.1.1 (was workspace:^)
    CM-->>Jenkins: Provide catalog-model@0.1.1
    
    Jenkins->>PCR: Request v0.0.1 (was workspace:^)
    PCR-->>Jenkins: Provide catalog-react@0.0.1
    
    Jenkins->>PJC: Request v0.1.0 (was workspace:^)
    PJC-->>Jenkins: Provide jenkins-common@0.1.0
    
    Note over Jenkins: Dependencies locked to<br/>specific versions
    
    PM-->>Dev: Dependencies resolved and installed

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.

[github-actions]

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!