[Snyk] Security upgrade @backstage/plugin-permission-common from 0.0.0-use.local to 0.1.0

[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-common/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 the @backstage/plugin-permission-common dependency to a specific version in the example-todo-list-common plugin.

• Changed dependency version from workspace:^ to 0.1.0 in package.json
• Transitions from local workspace reference to published package version
• Indicates preparation for package publication or migration from monorepo development setup

[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 upgrading the @backstage/plugin-permission-common dependency. This upgrade targets and resolves six distinct vulnerabilities, ranging from medium to high severity, thereby mitigating potential security risks within the application.

Highlights

• Security Upgrade: Automated upgrade of the @backstage/plugin-permission-common dependency to version 0.1.0 to address multiple identified security vulnerabilities.
• Vulnerabilities Addressed: This PR fixes six vulnerabilities, including Improper Handling of Unicode Encoding, Use of a Cryptographic Primitive with a Risky Implementation, UNIX Symbolic Link Following, two instances of Prototype Pollution, and Regular Expression Denial of Service (ReDoS).
• Manual Intervention Required: The yarn.lock file failed to update automatically, requiring manual intervention to update it before merging, especially for users leveraging 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. ↩

[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 pull request, automatically generated by Snyk, aims to fix several security vulnerabilities by upgrading the @backstage/plugin-permission-common package. However, the proposed change is incorrect and potentially harmful. It replaces a yarn workspace dependency (workspace:^) with a pinned, much older version (0.1.0), effectively downgrading it from the current workspace version of 0.7.7. This change breaks the monorepo's integrity and is likely to cause build failures or regressions. Additionally, the PR notes that it failed to update the yarn.lock file. Due to these critical issues, this PR should not be merged as is. The underlying vulnerabilities should be addressed by updating the dependencies within the @backstage/plugin-permission-common package itself or by other means that respect the monorepo structure.

[gemini-code-assist]

This change from workspace:^ to a pinned version 0.1.0 is incorrect and will likely cause issues. The workspace:^ protocol ensures that this package uses the local version of @backstage/plugin-permission-common from this monorepo, which is currently at version 0.7.7. Changing this to 0.1.0 is a significant downgrade and will cause this package to use an old, published version from the registry instead of the local one. This breaks the monorepo development workflow and could introduce bugs or break compatibility. This change should be reverted to keep the workspace dependency.

Suggested change

	"@backstage/plugin-permission-common": "0.1.0"
	"@backstage/plugin-permission-common": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the example-todo-list-common plugin by transitioning from a workspace protocol reference to a fixed version for the @backstage/plugin-permission-common package. The change replaces the flexible workspace:^ reference with a pinned version 0.1.0, indicating a shift from local monorepo development to using published package versions. This type of change is typically made when preparing a package for publication or when moving away from a workspace-based development setup to ensure consistent dependency resolution across different environments.

Changes

File(s)	Summary
plugins/example-todo-list-common/package.json	Updated @backstage/plugin-permission-common dependency from workspace protocol reference (workspace:^) to fixed version 0.1.0.

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

    Note over Dev,Plugin: Dependency Resolution Change

    rect rgb(240, 240, 240)
        Note over Dev,NPM: BEFORE: workspace:^ reference
        Dev->>PM: Install dependencies
        PM->>WS: Resolve @backstage/plugin-permission-common
        WS-->>PM: Return local workspace package
        PM->>Plugin: Link workspace dependency
    end

    rect rgb(220, 250, 220)
        Note over Dev,NPM: AFTER: 0.1.0 specific version
        Dev->>PM: Install dependencies
        PM->>NPM: Fetch @backstage/plugin-permission-common@0.1.0
        NPM-->>PM: Return published package v0.1.0
        PM->>Plugin: Install versioned dependency
    end

    Note over Plugin: Plugin now uses published<br/>package instead of<br/>workspace reference

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.