[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/user-settings/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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	210
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	113
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Prototype Pollution SNYK-JS-LODASHES-15053836	88
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	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)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

This PR transitions the user-settings plugin from workspace dependencies to pinned package versions.

• Changed @backstage/core-app-api from workspace:^ to 0.1.0
• Changed @backstage/core-components from workspace:^ to 0.1.0
• Changed @backstage/plugin-catalog-react from workspace:^ to 0.0.1
• Changed @backstage/theme from workspace:^ to 0.1.1
• Indicates preparation for independent distribution or stricter version control

[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 six identified vulnerabilities within its yarn dependencies. The changes primarily involve updating specific @backstage package versions in the plugins/user-settings/package.json file. Reviewers should note the requirement for a manual yarn.lock update and the implications for zero-install users.

Highlights

• Automated Security Fix: This pull request was automatically generated by Snyk to address 6 identified security vulnerabilities in the project's yarn dependencies.
• Dependency Updates: Several @backstage dependencies in plugins/user-settings/package.json have been updated to specific versions (e.g., @backstage/core-app-api to 0.1.0, @backstage/theme to 0.1.1) to resolve these vulnerabilities.
• Vulnerabilities Addressed: The fixes target issues including Improper Handling of Unicode Encoding, Risky Cryptographic Primitive Implementation, UNIX Symbolic Link Following, Prototype Pollution (two instances), and Regular Expression Denial of Service (ReDoS).
• Manual yarn.lock Update Required: A warning indicates that yarn.lock failed to update and requires manual intervention before merging.
• Zero-Install Note: Users leveraging Yarn's zero-install feature will need to run yarn locally to update their .yarn/cache/ directory.

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.

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the user-settings plugin by replacing workspace protocol references with explicit version numbers for four Backstage packages. The changes transition from monorepo-style workspace dependencies (workspace:^) to pinned versions: @backstage/core-app-api and @backstage/core-components are set to version 0.1.0, @backstage/plugin-catalog-react to 0.0.1, and @backstage/theme to 0.1.1. This modification suggests preparation for independent plugin distribution or establishing stricter version control over dependencies, moving away from the flexible workspace dependency resolution to explicit version pinning.

Changes

File(s)	Summary
plugins/user-settings/package.json	Updated four Backstage package dependencies from workspace protocol references (workspace:^) to explicit versions: @backstage/core-app-api (0.1.0), @backstage/core-components (0.1.0), @backstage/plugin-catalog-react (0.0.1), and @backstage/theme (0.1.1).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant PKG as user-settings/package.json
    participant WS as Workspace Registry
    participant NPM as NPM Registry
    
    Note over PM,NPM: Dependency Resolution Change
    
    PM->>PKG: Read dependencies
    
    alt Before PR (workspace references)
        PKG-->>PM: workspace:^ versions
        PM->>WS: Resolve @backstage/core-app-api
        WS-->>PM: Local workspace version
        PM->>WS: Resolve @backstage/core-components
        WS-->>PM: Local workspace version
    else After PR (fixed versions)
        PKG-->>PM: Specific version numbers
        PM->>NPM: Fetch @backstage/core-app-api@0.1.0
        NPM-->>PM: Package from registry
        PM->>NPM: Fetch @backstage/core-components@0.1.0
        NPM-->>PM: Package from registry
        PM->>NPM: Fetch @backstage/plugin-catalog-react@0.0.1
        NPM-->>PM: Package from registry
        PM->>NPM: Fetch @backstage/theme@0.1.1
        NPM-->>PM: Package from registry
    end
    
    PM->>PM: Install dependencies
    Note over PM: Build process can now use<br/>fixed versions instead of<br/>workspace references

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 automated Snyk pull request attempts to fix security vulnerabilities, but the proposed changes are incorrect for this monorepo and will likely break the application. It incorrectly replaces workspace:^ dependencies with old, pinned versions, which is a major downgrade. Additionally, the yarn.lock file is missing, which is critical for reproducible builds. It's recommended to reject these changes and instead address the vulnerabilities by updating the underlying transitive dependencies, for example, using Yarn's resolutions feature.

[gemini-code-assist]

These dependency versions are incorrectly pinned to old versions, replacing the workspace:^ protocol. This monorepo uses Yarn workspaces, where workspace:^ links to other local packages. Pinning @backstage/core-app-api to 0.1.0 when the local version is 1.9.1-next.0 is a major downgrade that will likely break the application. These changes should be reverted. To fix the security vulnerabilities, identify the vulnerable transitive dependencies and force updated versions, for instance, by using a resolutions block in the root package.json.

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