[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/github-deployments/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 github-deployments plugin dependencies from workspace protocol to explicit version pinning.

• Changed @backstage/catalog-model from workspace protocol to version 0.1.1
• Changed @backstage/integration-react from workspace protocol to version 0.1.1
• Changed @backstage/plugin-catalog-react from workspace protocol to version 0.0.1
• Enables standalone package publishing or controlled 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 project's security posture by resolving two identified vulnerabilities within its yarn dependencies. The changes involve updating specific package versions to their patched counterparts, thereby mitigating potential risks associated with Regular Expression Denial of Service and resource allocation issues.

Highlights

• Security Vulnerability Fix: This PR, automatically generated by Snyk, addresses two security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) and a medium-severity Allocation of Resources Without Limits or Throttling.
• Dependency Updates: The fix involves updating specific @backstage dependencies in plugins/github-deployments/package.json to newer versions to mitigate the identified vulnerabilities.
• Manual yarn.lock Update Required: A warning is noted that yarn.lock was not automatically updated and requires manual intervention before merging, especially for projects using Yarn's zero-installs feature.

Changelog

• plugins/github-deployments/package.json
  • Updated @backstage/catalog-model from workspace:^ to 0.1.1.
  • Updated @backstage/integration-react from workspace:^ to 0.1.1.
  • Updated @backstage/plugin-catalog-react from workspace:^ to 0.0.1.

Activity

• Snyk automatically created this pull request to fix 2 vulnerabilities.
• A warning was issued that yarn.lock failed to update and requires manual intervention.
• Snyk provided links to view the latest project report, customize PR templates, adjust project settings, and read about Snyk's upgrade logic.
• Snyk also provided links to free interactive lessons on the identified vulnerability types.

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.

[socket-security]

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		License policy violation: npm atob under CC-BY-3.0 License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS) From: ? → npm/atob@2.1.2 ℹ 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/atob@2.1.2. 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]

Walkthrough

This PR updates the dependency management strategy for the github-deployments plugin by transitioning three Backstage package dependencies from workspace protocol references to explicit version pinning. The affected packages are @backstage/catalog-model (pinned to 0.1.1), @backstage/integration-react (pinned to 0.1.1), and @backstage/plugin-catalog-react (pinned to 0.0.1). This change moves away from monorepo workspace references to fixed version specifications, which is typically done when preparing a plugin for standalone publication or implementing stricter dependency version control to ensure consistent behavior across different environments.

Changes

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

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace Registry
    participant NPM as NPM Registry
    participant GHD as github-deployments Plugin

    Dev->>PM: Install dependencies
    PM->>GHD: Read package.json
    
    Note over GHD,NPM: Before: workspace:^ references
    
    alt catalog-model (Changed to 0.1.1)
        PM->>NPM: Fetch @backstage/catalog-model@0.1.1
        NPM-->>PM: Return pinned version
    end
    
    alt integration-react (Changed to 0.1.1)
        PM->>NPM: Fetch @backstage/integration-react@0.1.1
        NPM-->>PM: Return pinned version
    end
    
    alt plugin-catalog-react (Changed to 0.0.1)
        PM->>NPM: Fetch @backstage/plugin-catalog-react@0.0.1
        NPM-->>PM: Return pinned version
    end
    
    alt Other dependencies (Still workspace:^)
        PM->>WS: Resolve workspace dependencies
        WS-->>PM: Return local workspace versions
    end
    
    PM->>GHD: Install all resolved dependencies
    PM-->>Dev: Installation complete
    
    Note over Dev,GHD: Result: Specific versions pinned,<br/>reducing version drift

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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix two security vulnerabilities by pinning several dependencies to old versions. This approach is incorrect for this monorepo as it breaks the yarn workspace setup by replacing workspace:^ specifiers with outdated, fixed versions. This will likely cause build failures or runtime issues. I have left a critical comment with a suggestion to revert the changes and an explanation of the correct manual fix, which involves updating the vulnerable transitive dependencies in their respective packages.

[gemini-code-assist]

This automated change is incorrect for this monorepo. It replaces workspace-local dependencies (workspace:^) with fixed, very old versions from the public registry. This will likely break the build and the application.

The correct way to fix the reported vulnerabilities is to update the transitive dependencies (ajv, qs) in the packages where they are defined (@backstage/catalog-model and @backstage/core-components respectively) and then update the yarn.lock file.

Please revert these changes and apply the fix manually.

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

[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!