[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/techdocs-addons-test-utils/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 transitions dependency specifications from workspace protocol to explicit semantic versions in the techdocs-addons-test-utils plugin.

• Changed 6 Backstage package dependencies from workspace:^ to specific versions (0.1.0 or 0.1.1)
• Affected packages: core-app-api, core-components, plugin-techdocs, plugin-techdocs-react, test-utils, and theme
• Modified in plugins/techdocs-addons-test-utils/package.json
• Indicates transition from monorepo workspace dependencies to published package versions

[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 involve updating several @backstage package versions to their latest secure counterparts in a specific package.json file, thereby mitigating potential security risks.

Highlights

• Vulnerability Fixes: This pull request addresses 6 security vulnerabilities identified by Snyk in the project's yarn dependencies, including high-severity issues like UNIX Symbolic Link Following and medium-severity issues such as Prototype Pollution and Regular Expression Denial of Service.
• Dependency Updates: Several @backstage package dependencies within plugins/techdocs-addons-test-utils/package.json have been updated from workspace:^ to specific, versioned releases (e.g., @backstage/core-app-api to 0.1.0, @backstage/plugin-techdocs to 0.1.1).
• Manual yarn.lock Update Required: Snyk reported that it failed to automatically update the yarn.lock file. A manual update of this file is required before merging to ensure all dependency changes are correctly reflected and to maintain consistency.

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. 2 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (2)
⛔	Open Source Security	0	0	2	0	2 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, attempts to fix security vulnerabilities by updating dependencies in plugins/techdocs-addons-test-utils/package.json. However, the proposed changes are incorrect for this monorepo setup. It replaces workspace: package links with pinned, outdated versions, which will likely break the project. My review includes a critical comment explaining why these changes should be reverted and suggests an alternative approach to resolving the vulnerabilities.

[gemini-code-assist]

These changes incorrectly replace workspace:^ dependencies with pinned, outdated versions. This will likely break the build and local development workflow.

In a Yarn workspace monorepo, workspace:^ is used to link to other packages within the same monorepo. By removing it and pinning to old versions, you are forcing this package to use old, published versions from the registry instead of the current code in your local repository.

For example:

• @backstage/core-app-api is being downgraded from the workspace version (likely 1.9.1-next.0 based on the repo) to 0.1.0.
• @backstage/core-components is being downgraded from its workspace version (e.g., 0.13.4-next.0) to 0.1.0.

This is a significant downgrade and will almost certainly cause issues.

While this PR was automatically generated by Snyk to fix vulnerabilities, the proposed changes are not suitable for this project's structure. The correct approach would be to identify the vulnerable transitive dependencies and update them, or update the @backstage packages themselves, while retaining the workspace:^ protocol. The PR also notes that yarn.lock was not updated, which is another critical issue.

I recommend reverting these changes and addressing the vulnerabilities by other means, such as updating the relevant packages across the monorepo and regenerating the lockfile.

    "@backstage/core-app-api": "workspace:^",
    "@backstage/core-components": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/integration-react": "workspace:^",
    "@backstage/plugin-catalog": "workspace:^",
    "@backstage/plugin-search-react": "workspace:^",
    "@backstage/plugin-techdocs": "workspace:^",
    "@backstage/plugin-techdocs-react": "workspace:^",
    "@backstage/test-utils": "workspace:^",
    "@backstage/theme": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the techdocs-addons-test-utils plugin by transitioning from workspace protocol references to explicit semantic versioning. Six Backstage packages are affected, moving from workspace:^ to specific version numbers (0.1.0 or 0.1.1). This change typically indicates preparation for package publication or a shift in how dependencies are managed within the monorepo structure. The affected packages include core components, testing utilities, and TechDocs-related plugins, ensuring they reference specific published versions rather than workspace-relative dependencies.

Changes

File(s)	Summary
plugins/techdocs-addons-test-utils/package.json	Updated 6 Backstage package dependencies from workspace protocol (workspace:^) to explicit semantic versions (0.1.0-0.1.1), including @backstage/core-app-api, @backstage/core-components, @backstage/plugin-techdocs, @backstage/plugin-techdocs-react, @backstage/test-utils, and @backstage/theme.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Deps as Dependencies
    
    Note over Dev,Deps: Dependency Version Pinning Process
    
    Dev->>PM: Update package.json
    Note right of Dev: Change workspace:^ to<br/>specific versions
    
    PM->>Deps: Resolve @backstage/core-app-api@0.1.0
    PM->>Deps: Resolve @backstage/core-components@0.1.0
    PM->>Deps: Resolve @backstage/plugin-techdocs@0.1.1
    PM->>Deps: Resolve @backstage/plugin-techdocs-react@0.1.0
    PM->>Deps: Resolve @backstage/test-utils@0.1.1
    PM->>Deps: Resolve @backstage/theme@0.1.1
    
    Deps-->>PM: Return resolved packages
    PM-->>Dev: Dependencies locked to specific versions
    
    Note over Dev,Deps: No runtime behavior changes<br/>Only build-time dependency resolution

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.