[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/catalog-import/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 created by Snyk, focuses on enhancing the project's security posture by upgrading several key dependencies within the plugins/catalog-import module. The changes are designed to mitigate a range of identified vulnerabilities, ensuring the application remains robust against common security threats. Reviewers should pay close attention to the dependency version bumps and the explicit note regarding the manual update of the yarn.lock file to prevent potential build or runtime issues.

Highlights

• Automated Vulnerability Fix: This pull request was automatically generated by Snyk to address 6 identified security vulnerabilities in the project's yarn dependencies.
• Dependency Updates: Key dependencies in plugins/catalog-import/package.json have been updated, including @backstage/core-components, @backstage/integration, @backstage/integration-react, @backstage/plugin-catalog-react, and lodash.
• Vulnerabilities Addressed: The updates aim to fix issues such as Directory Traversal (SNYK-JS-TAR-15032660), UNIX Symbolic Link Following (SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291), Prototype Pollution (SNYK-JS-LODASH-15053838, SNYK-JS-LODASHES-15053836), Regular Expression Denial of Service (ReDoS) (SNYK-JS-DIFF-14917201), and Uncontrolled Recursion (SNYK-JS-ESLINT-15102420).
• Manual yarn.lock Update Required: A warning indicates that the yarn.lock file was not automatically updated and requires manual intervention before merging, especially for projects utilizing Yarn's zero-installs feature.

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

[gemini-code-assist]

Code Review

This pull request updates several dependencies in plugins/catalog-import/package.json to address multiple reported vulnerabilities, including a lodash prototype pollution issue. While the package.json reflects these updates, it's crucial to manually update the yarn.lock file to ensure these fixes are properly applied. Additionally, the change from workspace:^ to fixed versions for internal @backstage dependencies should be reviewed for its impact on the monorepo's dependency resolution strategy.

[gemini-code-assist]

The dependencies @backstage/core-components, @backstage/integration, @backstage/integration-react, and @backstage/plugin-catalog-react have been changed from workspace:^ to specific version numbers. In a monorepo setup, workspace:^ typically ensures that local versions of these packages are used. Changing to fixed versions might alter how these dependencies are resolved, potentially leading to inconsistencies with other workspace packages or unexpected behavior during local development. Please confirm if this change in dependency resolution strategy is intended for these specific packages, or if it should revert to workspace:^ after the vulnerability fix is verified.

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