[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):

• 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
	Directory Traversal SNYK-JS-TAR-15032660	149
	Directory Traversal SNYK-JS-TAR-15127355	127
	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:

🦉 Directory Traversal

---

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

[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, focuses on improving the project's security by updating a key dependency. The primary objective is to remediate several identified medium-severity vulnerabilities, thereby enhancing the overall robustness and safety of the application's dependencies.

Highlights

• Dependency Upgrade: The @backstage/types dependency has been upgraded from 0.0.0-use.local (implied by workspace:^) to version 0.1.1.
• Security Vulnerabilities Addressed: This upgrade fixes three medium-severity vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
• Yarn Zero-Installs Consideration: Users leveraging Yarn's zero-installs feature will need to manually run yarn to update the .yarn/cache/ directory, as this PR does not include that update.
• Manual yarn.lock Update Required: The automated process failed to update the yarn.lock file, which requires manual intervention before this pull request can be merged.

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]

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		License policy violation: npm atob under CC-BY-3.0 License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS) From: ? → npm/atob@2.1.2 ℹ 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/atob@2.1.2. 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

[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 from "workspace:^" to "0.1.1" is incorrect for this monorepo. It replaces the workspace-local dependency with a specific, older version from the registry, which is effectively a downgrade from the local version 1.1.0. This breaks the monorepo's dependency management and should be reverted. The vulnerabilities should be addressed by updating the @backstage/types package or its dependencies directly, not by pinning a version in a consuming package.

[gemini-code-assist]

This change from "workspace:^" to a specific version "0.1.1" is incorrect in a Yarn workspace monorepo. It breaks the link to the local @backstage/types package and instead pulls an older version from the registry. The local version of @backstage/types is 1.1.0, so this is a downgrade that could cause issues. The dependency should be kept as "workspace:^" to maintain consistency within the monorepo.

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

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