[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1

[q1blue]

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

Snyk changed the following file(s):

• plugins/tech-insights-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
	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 pins the @backstage/types dependency to a specific version in the tech-insights-common plugin package.

• Changed dependency reference from workspace:^ to 0.1.1 in plugins/tech-insights-common/package.json
• Standardizes dependency management for package publication
• Ensures consistent dependency resolution across environments

[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 focuses on enhancing the project's security by upgrading a key dependency, @backstage/types. The update specifically targets and resolves critical vulnerabilities, ensuring a more secure and stable application environment. Reviewers should pay close attention to the manual yarn.lock update requirement.

Highlights

• Security Upgrade: Upgraded the @backstage/types dependency from workspace:^ to 0.1.1 to address three identified vulnerabilities: two Server-side Request Forgery (SSRF) issues and one Allocation of Resources Without Limits or Throttling issue.
• Automated Fix: This pull request was automatically generated by Snyk to remediate the detected security vulnerabilities.
• Manual Intervention Required: The yarn.lock file failed to update automatically and requires manual intervention before merging. Users of Yarn's zero-installs feature will also need to run yarn to update their .yarn/cache/ directory.

Changelog

• plugins/tech-insights-common/package.json
  • Updated the @backstage/types dependency to version 0.1.1.

Activity

• This pull request was automatically created by Snyk to fix 3 vulnerabilities in the yarn dependencies.
• A warning was noted that the yarn.lock file failed to update and requires manual update before merging.
• The PR advises users of Yarn's zero-installs feature to run yarn to update their .yarn/cache/ directory.

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 security vulnerabilities by upgrading the @backstage/types package. However, the proposed change is incorrect. It replaces a yarn workspace dependency (workspace:^) with a pinned, and significantly older, version (0.1.1). This would break the monorepo's dependency linking and downgrade the package from version 1.1.0 to 0.1.1, likely causing build failures and other issues. The review includes a critical comment recommending the rejection of this change because Snyk appears to have misinterpreted the project's dependency setup.

[gemini-code-assist]

This automated change is incorrect and should be rejected. It replaces the yarn workspace dependency with a pinned, and much older, version of @backstage/types.

1. Breaks Workspace Linking: Changing "workspace:^" to "0.1.1" will cause yarn to fetch this package from the npm registry instead of linking to the local @backstage/types package within this monorepo. This is a fundamental change to how dependencies are managed in this project.

2. Significant Downgrade: The suggested version 0.1.1 is a major downgrade. The local @backstage/types package is at version 1.1.0. This downgrade would likely cause build failures or runtime errors, as tech-insights-common depends on features from newer versions of @backstage/types.

It appears Snyk has misinterpreted the workspace:^ protocol, which is also indicated by the warning in the PR description about failing to update yarn.lock. The vulnerabilities it aims to fix may already be resolved in the 1.1.0 version currently in use via the workspace. This PR should be closed. If vulnerabilities persist, the dependencies of the @backstage/types package should be updated directly.

Suggested change

	"@backstage/types": "0.1.1",
	"@backstage/types": "workspace:^",

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the @backstage/types package in the tech-insights-common plugin. The change transitions from using a workspace protocol reference to a pinned version (0.1.1), which standardizes dependency versioning and indicates the package is being prepared for independent publication or distribution outside the monorepo workspace. This ensures consistent dependency resolution and makes the package more portable for external consumers.

Changes

File(s)	Summary
plugins/tech-insights-common/package.json	Updated @backstage/types dependency from workspace protocol reference (workspace:^) to fixed version 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 TIC as tech-insights-common

    Note over Dev,TIC: Dependency Resolution Change

    Dev->>PM: Install dependencies
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/types
        WS-->>PM: Return local workspace version
        PM->>TIC: Link workspace version
    else After Change (0.1.1)
        PM->>NPM: Fetch @backstage/types@0.1.1
        NPM-->>PM: Return version 0.1.1
        PM->>TIC: Install specific version 0.1.1
    end
    
    Note over TIC: Package now uses<br/>pinned version instead<br/>of 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.

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