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

[q1blue]

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

Snyk changed the following file(s):

• packages/core-plugin-api/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 standardizes dependency management by replacing a workspace protocol reference with a fixed version for the @backstage/types package.

• Changed @backstage/types dependency from workspace:^ to version 0.1.1
• Updated in packages/core-plugin-api/package.json
• Transitions from local workspace dependency to published package version
• Likely part of package release preparation or monorepo dependency standardization

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

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/types dependency. This update resolves six identified vulnerabilities, ranging from medium to high severity, thereby mitigating potential security risks within the application.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, upgrades the @backstage/types dependency to address multiple security vulnerabilities.
• Vulnerability Fixes: The upgrade resolves 6 identified vulnerabilities, including high-severity issues like UNIX Symbolic Link Following and medium-severity issues such as Prototype Pollution and Regular Expression Denial of Service (ReDoS).
• Dependency Version Bump: The @backstage/types package has been updated from 0.0.0-use.local (or workspace:^) to version 0.1.1.
• Yarn Lock Warning: A warning is present indicating that the yarn.lock file was not automatically updated and requires manual intervention, particularly for projects utilizing 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. ↩

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the @backstage/types package in the core plugin API. The change transitions from using a workspace protocol reference to a fixed version number (0.1.1). This modification is part of standardizing dependency versioning across the monorepo, likely in preparation for a package release or to ensure consistent dependency resolution. The update moves away from local workspace dependencies to published package versions, which is a common practice when preparing packages for distribution or when stabilizing the dependency graph in a monorepo environment.

Changes

File(s)	Summary
packages/core-plugin-api/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 Workspace as Local Workspace
    participant Registry as NPM Registry
    participant CoreAPI as @backstage/core-plugin-api

    Note over Dev,Registry: Before: workspace:^ dependency

    Dev->>PM: Build/Install dependencies
    PM->>Workspace: Resolve @backstage/types (workspace:^)
    Workspace-->>PM: Return local package
    PM->>CoreAPI: Link local @backstage/types

    Note over Dev,Registry: After: 0.1.1 dependency (This PR)

    Dev->>PM: Build/Install dependencies
    PM->>Registry: Fetch @backstage/types@0.1.1
    Registry-->>PM: Return published package v0.1.1
    PM->>CoreAPI: Install @backstage/types@0.1.1

    Note over CoreAPI: Now uses published version<br/>instead 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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, incorrectly downgrades the @backstage/types package. It changes the version from workspace:^, which resolves to the current workspace version (1.1.0), to a hardcoded 0.1.1. This is a significant downgrade that will likely cause issues. The workspace: protocol is the standard and correct way to reference other packages within this monorepo.

This change should be rejected. The reported vulnerabilities should be addressed manually, for example by running yarn upgrade for the affected transitive dependencies and updating the yarn.lock file.

Additionally, I've noticed that other dependencies in this package.json like @backstage/config and @backstage/version-bridge are also pinned to outdated versions, which is inconsistent with the project's changelog. It would be beneficial to investigate this and potentially update them to use workspace:^ as well to ensure consistency and correctness across the monorepo.

[gemini-code-assist]

This change incorrectly downgrades @backstage/types to version 0.1.1. The workspace:^ specifier correctly resolves to version 1.1.0 of the package from within this monorepo, as can be seen in packages/types/package.json. Hardcoding an old version is incorrect and will likely cause problems. This should be reverted to use the workspace protocol to ensure the correct version is used.

Suggested change

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