[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/events-backend-module-azure/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 Azure events backend module from workspace protocol dependencies to explicit version numbers.

• Changed @backstage/backend-plugin-api from workspace:^ to 0.6.19
• Changed @backstage/plugin-events-node from workspace:^ to 0.2.9
• Modified plugins/events-backend-module-azure/package.json
• Indicates preparation for package release or dependency management standardization

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[snyk-io]

✅ 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.

[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 critical vulnerabilities within the plugins/events-backend-module-azure package. It achieves this by upgrading specific dependencies to their patched versions. While the package.json has been updated, a manual step is required to update the yarn.lock file, and zero-install users should be aware of an additional yarn command needed.

Highlights

• Security Vulnerability Fixes: This PR addresses two identified vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) and a medium-severity Allocation of Resources Without Limits or Throttling issue.
• Dependency Version Upgrades: The package.json file for plugins/events-backend-module-azure has been updated to specific versions for @backstage/backend-plugin-api (to 0.6.19) and @backstage/plugin-events-node (to 0.2.9).
• Manual yarn.lock Update Required: The automated process failed to update yarn.lock, necessitating a manual update before merging to ensure consistency.
• Zero-Install User Guidance: Users leveraging Yarn's zero-installs feature are advised to run yarn after pulling this PR to update their .yarn/cache directory.

Changelog

• plugins/events-backend-module-azure/package.json
  • Updated @backstage/backend-plugin-api from workspace:^ to 0.6.19.
  • Updated @backstage/plugin-events-node from workspace:^ to 0.2.9.

Activity

• Snyk automatically created this pull request to address identified security vulnerabilities.
• The automated process attempted to update yarn.lock but reported a failure, indicating a manual update is required.

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. ↩

[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 Azure events backend module plugin. The changes transition from workspace protocol references to explicit version numbers for two Backstage dependencies. Specifically, @backstage/backend-plugin-api is pinned to version 0.6.19 and @backstage/plugin-events-node to version 0.2.9. This modification suggests preparation for package publication or a shift towards standardized dependency versioning, moving away from monorepo workspace dependency resolution to fixed version specifications that provide more predictable and stable dependency resolution.

Changes

File(s)	Summary
plugins/events-backend-module-azure/package.json	Updated dependency specifications from workspace protocol (workspace:^) to explicit versions: @backstage/backend-plugin-api to 0.6.19 and @backstage/plugin-events-node to 0.2.9.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant Azure as events-backend-module-azure
    participant BPA as backend-plugin-api
    participant EPN as plugin-events-node

    Note over PM,EPN: Dependency Resolution During Installation

    PM->>Azure: Install package
    activate Azure
    
    Azure->>PM: Request backend-plugin-api@0.6.19
    PM->>BPA: Resolve and install v0.6.19
    activate BPA
    BPA-->>PM: Installed
    deactivate BPA
    
    Azure->>PM: Request plugin-events-node@0.2.9
    PM->>EPN: Resolve and install v0.2.9
    activate EPN
    EPN-->>PM: Installed
    deactivate EPN
    
    PM-->>Azure: Dependencies resolved
    deactivate Azure
    
    Note over Azure,EPN: Changed from workspace references<br/>to pinned versions

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, aims to fix two security vulnerabilities by updating dependencies in plugins/events-backend-module-azure/package.json. While addressing security issues is important, the current approach of pinning @backstage/backend-plugin-api and @backstage/plugin-events-node to specific versions is not ideal for a monorepo using Yarn workspaces. This change moves away from the workspace:^ protocol, which can lead to dependency inconsistencies and future maintenance challenges. A better approach would be to update the dependencies within the workspace packages to resolve the vulnerabilities. Furthermore, the PR description indicates a failure to update yarn.lock, which is a critical step that must be completed manually before merging.

[gemini-code-assist]

Pinning dependencies to specific versions instead of using workspace:^ goes against the conventions of a monorepo using Yarn workspaces. This change will cause this package to fall out of sync with the versions used across the rest of the repository, creating maintenance challenges and potential dependency conflicts.

The recommended approach is to address the vulnerabilities within the source packages (@backstage/backend-plugin-api and @backstage/plugin-events-node) and allow the updates to propagate through the workspace. This maintains a single version policy and simplifies dependency management.

    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/plugin-events-node": "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!