[Snyk] Fix for 6 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/events-backend-module-bitbucket-cloud/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
	Directory Traversal SNYK-JS-TAR-15032660	149
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	112
	Prototype Pollution SNYK-JS-LODASH-15053838	87
	Prototype Pollution SNYK-JS-LODASHES-15053836	87
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	61
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	45

---

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)
🦉 Prototype Pollution
🦉 Directory Traversal

[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 six critical vulnerabilities found in its yarn dependencies. The changes involve updating specific package versions within the plugins/events-backend-module-bitbucket-cloud/package.json file to their secure counterparts.

Highlights

• Dependency Vulnerability Fixes: This PR updates specific dependencies in plugins/events-backend-module-bitbucket-cloud/package.json to address 6 identified security vulnerabilities, including Directory Traversal, UNIX Symbolic Link Following, Prototype Pollution, Regular Expression Denial of Service (ReDoS), and Uncontrolled Recursion.
• Automated Dependency Updates: The @backstage/backend-plugin-api dependency has been updated from workspace:^ to 1.6.1, and @backstage/plugin-events-node has been updated from workspace:^ to 0.4.0.

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 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]

Code Review

This automated Snyk pull request updates two dependencies to fix security vulnerabilities. The change pins @backstage/backend-plugin-api and @backstage/plugin-events-node to specific versions, removing the workspace:^ specifier. While this resolves the vulnerabilities, it's important to be aware of the implications. As detailed in my review comment, this change decouples the package from the monorepo's workspace, which can create maintenance challenges. Furthermore, the PR description correctly notes that yarn.lock has not been updated. This must be done manually before merging to ensure the dependency fixes are actually applied.

[gemini-code-assist]

Pinning dependencies to specific versions instead of using workspace:^ decouples this package from the monorepo's versioning. While this change fixes the security vulnerabilities, it can lead to future maintenance issues and inconsistencies with other packages in the workspace. The preferred approach is typically to update the dependency versions across the entire workspace to resolve vulnerabilities while maintaining workspace integrity. If this change is merged, be aware of the potential for this package to fall out of sync with API changes in @backstage/backend-plugin-api and @backstage/plugin-events-node.