[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/example-todo-list/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	208
	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 pins Backstage dependencies to specific versions in the example-todo-list plugin package configuration.

• Changed @backstage/core-components from workspace:^ to fixed version 0.1.0
• Changed @backstage/theme from workspace:^ to fixed version 0.1.1
• Transitions from monorepo workspace references to explicit version specifications
• Modified in plugins/example-todo-list/package.json

[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, focuses on enhancing the project's security posture by resolving six identified vulnerabilities within its Yarn dependencies. The changes involve precise version updates for two core Backstage dependencies in a specific plugin's package.json, aiming to mitigate risks associated with issues like Prototype Pollution, ReDoS, and Symlink Following.

Highlights

• Vulnerability Fixes: This PR addresses 6 identified security vulnerabilities in the project's yarn dependencies, including issues related to Improper Handling of Unicode Encoding, Use of a Cryptographic Primitive with a Risky Implementation, UNIX Symbolic Link Following, Prototype Pollution, and Regular Expression Denial of Service (ReDoS).
• Dependency Updates: The plugins/example-todo-list/package.json file has been updated to specify exact versions for @backstage/core-components (to 0.1.0) and @backstage/theme (to 0.1.1), moving away from workspace:^.
• Manual yarn.lock Update Required: Users employing Yarn's zero-installs feature will need to manually run yarn to update the .yarn/cache/ directory and yarn.lock file, as Snyk was unable to update yarn.lock automatically.

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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix several vulnerabilities by modifying dependencies. However, the proposed changes are incorrect for this monorepo project. It replaces workspace:^ dependencies with specific, outdated versions for @backstage/core-components and @backstage/theme. This breaks the monorepo's dependency management strategy, which relies on using local packages from the workspace.

The changes would cause significant downgrades and likely lead to build failures, runtime errors, or other inconsistencies. As noted in the PR description, yarn.lock also failed to update, indicating issues with the automated process.

I have added a critical comment to revert these changes. It is strongly recommended to close this PR and address the vulnerabilities manually, for instance by using resolutions in the root package.json to force newer, non-vulnerable versions of transitive dependencies.

[gemini-code-assist]

These changes incorrectly replace workspace dependencies with fixed, much older versions. In this monorepo setup, "workspace:^" ensures that this plugin uses the @backstage/core-components and @backstage/theme packages from this same repository.

• @backstage/core-components would be downgraded from workspace version 0.13.4-next.0 to 0.1.0.
• @backstage/theme would be downgraded from workspace version 0.4.1 to 0.1.1.

Pinning to these outdated versions from the npm registry will break the monorepo's dependency integrity and likely cause version mismatches, build failures, or runtime errors. These changes should be reverted. To fix the underlying vulnerabilities, consider using resolutions in the root package.json or updating the vulnerable transitive dependencies through their direct parents.

    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/theme": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates dependency management for the example-todo-list plugin by transitioning from workspace protocol references to fixed version specifications. The changes pin two Backstage packages to specific versions: @backstage/core-components is set to version 0.1.0 and @backstage/theme to version 0.1.1. This modification replaces the flexible workspace:^ protocol with explicit version numbers, which typically indicates preparation for package publication or a shift from monorepo workspace dependencies to using published package versions from the npm registry.

Changes

File(s)	Summary
plugins/example-todo-list/package.json	Updated dependency specifications from workspace protocol (workspace:^) to fixed versions: @backstage/core-components to 0.1.0 and @backstage/theme to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace
    participant NPM as NPM Registry
    participant Plugin as example-todo-list

    Note over Dev,Plugin: Dependency Resolution Change

    Dev->>Plugin: Update package.json
    Note right of Plugin: Pin versions:<br/>core-components: 0.1.0<br/>theme: 0.1.1

    Dev->>PM: Run install command
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/core-components
        WS-->>PM: Return local workspace version
        PM->>WS: Resolve @backstage/theme
        WS-->>PM: Return local workspace version
    else After Change (specific versions)
        PM->>NPM: Fetch @backstage/core-components@0.1.0
        NPM-->>PM: Return package
        PM->>NPM: Fetch @backstage/theme@0.1.1
        NPM-->>PM: Return package
    end

    PM->>Plugin: Install dependencies
    Plugin-->>Dev: Build ready with 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.