[Snyk] Fix for 4 vulnerabilities

[q1blue]

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• plugins/fossa/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
	Directory Traversal SNYK-JS-TAR-15127355	129
	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)
🦉 Directory Traversal

---

EntelligenceAI PR Summary

This PR pins Backstage dependencies in the fossa plugin to specific versions instead of using workspace protocol.

• Changed @backstage/core-components from workspace:^ to 0.8.6 in plugins/fossa/package.json
• Changed @backstage/theme from workspace:^ to 0.1.1 in plugins/fossa/package.json
• Replaces monorepo workspace resolution with explicit version pinning for compatibility or publication purposes

[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 aims to enhance the security posture of the project by automatically updating specific yarn dependencies within the plugins/fossa module. The changes are designed to mitigate known medium-severity vulnerabilities, ensuring a more secure and stable application environment by pinning exact dependency versions.

Highlights

• Security Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses four medium-severity security vulnerabilities (Directory Traversal, Regular Expression Denial of Service, and Uncontrolled Recursion) found in the project's yarn dependencies.
• Dependency Version Pinning: The plugins/fossa/package.json file has been updated to pin specific versions for @backstage/core-components to 0.8.6 and @backstage/theme to 0.1.1, moving away from workspace:^ declarations to resolve the identified vulnerabilities.

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 dependency management for the fossa plugin by replacing workspace protocol references with pinned versions for two Backstage packages. The @backstage/core-components dependency is locked to version 0.8.6 and @backstage/theme to version 0.1.1. This change moves away from monorepo workspace resolution (workspace:^) to explicit version pinning, which typically indicates preparation for external package publication or the need to ensure compatibility with specific versions of these dependencies.

Changes

File(s)	Summary
plugins/fossa/package.json	Updated @backstage/core-components from workspace:^ to pinned version 0.8.6 and @backstage/theme from workspace:^ to pinned version 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant FP as FOSSA Plugin
    participant CC as @backstage/core-components
    participant TH as @backstage/theme

    Note over PM,TH: Dependency Resolution Process

    PM->>FP: Read package.json
    FP-->>PM: Dependencies list
    
    alt Before Change (workspace:^)
        PM->>PM: Resolve workspace:^ references
        PM->>PM: Use local workspace versions
        Note over PM: Dynamic version from monorepo
    else After Change (pinned versions)
        PM->>CC: Fetch version 0.8.6
        CC-->>PM: Package installed
        PM->>TH: Fetch version 0.1.1
        TH-->>PM: Package installed
        Note over PM: Fixed versions from registry
    end

    PM->>FP: Dependencies installed
    Note over FP: Plugin ready with<br/>pinned dependency 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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix four security vulnerabilities by pinning @backstage/core-components and @backstage/theme to older, specific versions. However, this change is problematic in this monorepo as it breaks the workspace: protocol, which can lead to serious integration issues. I've left a comment with a recommendation to revert these changes and instead use yarn's resolutions feature to address the transitive dependency vulnerabilities without disrupting the monorepo structure. The PR also notes that yarn.lock was not updated, which would need to be addressed manually.

[gemini-code-assist]

This change pins @backstage/core-components and @backstage/theme to specific, outdated versions, replacing the workspace:^ specifier. This is a critical issue in a monorepo as it breaks the workspace protocol, likely leading to dependency conflicts, build failures, or runtime errors due to API incompatibilities.

The pinned versions (0.8.6 and 0.1.1) are significant downgrades from the current workspace versions (0.13.4-next.0 and 0.4.1 respectively).

While this was likely done to fix security vulnerabilities, this approach is incorrect. A better way to fix transitive dependency vulnerabilities in a yarn workspace is to use resolutions in the root package.json. This allows you to override vulnerable nested dependencies without breaking the workspace linking.

I recommend reverting these changes and using resolutions to address the Snyk vulnerabilities.

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