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

[q1blue]

Snyk has created this PR to fix 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157
	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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR standardizes dependency management by updating the @backstage/types dependency to a fixed version in the core plugin API package.

• Changed dependency version from workspace:^ to 0.1.1 in packages/core-plugin-api/package.json
• Transitions from local workspace dependency to published package version
• Prepares package for release or standardizes dependency management across monorepo

[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, performs a security upgrade by updating the @backstage/types dependency. The primary goal is to mitigate a high-severity Regular Expression Denial of Service (ReDoS) vulnerability and a medium-severity resource allocation vulnerability, enhancing the project's overall security posture.

Highlights

• Security Upgrade: Automated upgrade of the @backstage/types dependency from workspace:^ to 0.1.1 to address identified security vulnerabilities.
• Vulnerability Fixes: Fixes a high-severity Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-AJV-15274295) and a medium-severity Allocation of Resources Without Limits or Throttling vulnerability (SNYK-JS-QS-15268416).
• Yarn Lock Warning: The yarn.lock file was not automatically updated and requires manual intervention, particularly for projects utilizing Yarn's zero-install feature.

Changelog

• packages/core-plugin-api/package.json
  • Updated @backstage/types dependency version.

Activity

• This pull request was automatically created by Snyk to address identified security vulnerabilities.
• A warning was noted indicating that the yarn.lock file failed to update and requires manual intervention.

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​docusaurus/​module-type-aliases@​0.0.0-5591
	@​docusaurus/​preset-classic@​0.0.0-5591
	@​spotify/​prettier-config@​14.1.3
	@​docusaurus/​plugin-client-redirects@​0.0.0-5591
	@​docusaurus/​core@​0.0.0-5591
	@​types/​webpack-env@​1.18.1
	@​tsconfig/​docusaurus@​1.0.7
	@​types/​luxon@​3.3.0
	docusaurus-plugin-sass@​0.2.4
	clsx@​1.2.1
	js-yaml@​4.1.0
	luxon@​2.5.2 ⏵ 3.3.0	+3		+1
	@​swc/​core@​1.3.68

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code in npm @babel/traverse CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2; >= 8.0.0-alpha.0 < 8.0.0-alpha.4 Patched version: 7.23.2 From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/@babel/traverse@7.21.4 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@babel/traverse@7.21.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm argparse under Python-2.0.1 License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE) From: ? → npm/js-yaml@4.1.0 → npm/argparse@2.0.1 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/argparse@2.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/caniuse-lite@1.0.30001481 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001481. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/entities@4.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[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

    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: Dependency now points to<br/>published version instead of<br/>local workspace

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 resolve security vulnerabilities by upgrading @backstage/types. However, the proposed change is incorrect and will likely break the project. It replaces the Yarn workspace dependency (workspace:^) with a fixed, old version (0.1.1). The current version of @backstage/types in the workspace is 1.1.0, so this change is a significant downgrade. This will likely introduce breaking changes and inconsistencies within the monorepo. The correct approach would be to address the vulnerabilities within the @backstage/types package itself or ensure all related packages are updated consistently while respecting the workspace setup.

[gemini-code-assist]

This change incorrectly replaces the Yarn workspace dependency (workspace:^) with a fixed, outdated version. The current version of @backstage/types in this monorepo is 1.1.0, so changing this to 0.1.1 is a major downgrade and will likely cause build failures or runtime errors due to API incompatibilities.

To maintain consistency and correctness within the monorepo, this dependency should remain as workspace:^ to resolve to the local @backstage/types package.

Suggested change

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

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