[Snyk] Fix for 3 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/gcalendar/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
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	83
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	83
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)

---

EntelligenceAI PR Summary

This PR transitions the gcalendar plugin from workspace dependencies to fixed package versions for Backstage dependencies.

• Changed @backstage/core-components from workspace:^ to fixed version 0.1.0
• Changed @backstage/theme from workspace:^ to fixed version 0.1.1
• Prepares plugin for standalone publishing or alignment with specific upstream versions
• Modified only plugins/gcalendar/package.json

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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]

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, addresses three vulnerabilities in the plugins/gcalendar plugin by updating the @backstage/core-components and @backstage/theme dependencies. The PR aims to improve the security and stability of the project by incorporating the latest versions of these packages.

Highlights

• Dependency Updates: This PR updates the @backstage/core-components and @backstage/theme dependencies in the plugins/gcalendar/package.json file.
• Vulnerability Fixes: The updates address three vulnerabilities: two Server-Side Request Forgery (SSRF) issues and one Allocation of Resources Without Limits or Throttling issue.
• Snyk Automated PR: This pull request was automatically created by Snyk to resolve identified vulnerabilities.

Changelog

• plugins/gcalendar/package.json
  • Updated @backstage/core-components from workspace:^ to 0.1.0.
  • Updated @backstage/theme from workspace:^ to 0.1.1.

Activity

• Snyk identified and is attempting to fix vulnerabilities.
• The PR updates package.json to address security concerns.
• A warning indicates a failure to update yarn.lock, suggesting a manual update is needed before merging.

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. ↩

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the gcalendar plugin by transitioning from workspace protocol references to fixed package versions. Specifically, it pins @backstage/core-components to version 0.1.0 and @backstage/theme to version 0.1.1. This change moves away from local workspace dependencies to explicit published package versions, which is typically done when preparing a plugin for standalone distribution or ensuring compatibility with specific upstream Backstage releases. The modification affects only the package.json file and does not include any code changes.

Changes

File(s)	Summary
plugins/gcalendar/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 Plugin as gcalendar Plugin
    participant CoreComponents as @backstage/core-components
    participant Theme as @backstage/theme
    
    Note over Plugin,Theme: Dependency Version Update
    
    Note over Plugin: Before: Uses workspace protocol
    Plugin->>CoreComponents: depends on workspace:^
    Plugin->>Theme: depends on workspace:^
    
    Note over Plugin,Theme: After: Uses fixed versions
    Plugin->>CoreComponents: depends on 0.1.0
    Plugin->>Theme: depends on 0.1.1
    
    Note over Plugin,Theme: Change: Workspace references replaced<br/>with specific published 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 security vulnerabilities by pinning @backstage/core-components and @backstage/theme to specific, older versions. This approach is incorrect for this monorepo as it breaks the workspace-based dependency resolution and introduces significant downgrades that will likely cause build or runtime failures. The vulnerabilities should be addressed by updating the dependencies in their respective packages within the monorepo. Additionally, the PR failed to update the yarn.lock file. I've left a critical comment detailing why this PR should not be merged and what the correct course of action is.

[gemini-code-assist]

Pinning dependencies to old, fixed versions instead of using workspace:^ breaks the monorepo structure. This change will cause the gcalendar plugin to use outdated versions of @backstage/core-components (0.1.0 instead of the workspace version 0.13.4-next.0) and @backstage/theme (0.1.1 instead of 0.4.1), which will likely lead to build failures or runtime errors.

The correct approach to fix the security vulnerabilities is to update the transitive dependencies in their source packages within this repository. For instance, the qs vulnerability should be fixed by upgrading the qs version in packages/core-components/package.json.

Furthermore, the PR description notes that yarn.lock failed to update, which is another indication that these changes are not correct. It is highly recommended to close this PR and address the vulnerabilities at their source to maintain repository consistency and avoid breaking changes.

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!