Skip to content

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

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-e53db62c48ee7f347935bcc477baecdf
Closed

[Snyk] Security upgrade @backstage/types from 0.0.0-use.local to 0.1.1#11601
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-e53db62c48ee7f347935bcc477baecdf

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Feb 1, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/config/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
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity 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 pins the @backstage/types dependency to a specific version in the config package, replacing the workspace protocol reference.

  • Changed dependency version from workspace:^ to 0.1.1 in packages/config/package.json
  • Ensures consistent dependency resolution across different environments
  • Prepares package for publication with explicit version pinning

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 1, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! 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, generated by Snyk, focuses on enhancing the project's security by upgrading a core dependency. The change aims to mitigate known medium-severity vulnerabilities, ensuring a more secure and stable application environment. While the dependency version is updated, a follow-up manual step is required to fully integrate the changes into the project's dependency lockfile.

Highlights

  • Security Upgrade: This pull request automatically upgrades the @backstage/types dependency from workspace:^ (effectively 0.0.0-use.local) to 0.1.1 to address identified security vulnerabilities.
  • Vulnerabilities Addressed: The upgrade fixes three medium-severity vulnerabilities: two instances of Directory Traversal (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
  • Manual yarn.lock Update Required: Snyk reported a failure to update the yarn.lock file. Users, especially those utilizing Yarn's zero-installs feature, will need to manually run yarn to update the lockfile and .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.

@socket-security
Copy link
Copy Markdown

@socket-security
Copy link
Copy Markdown

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 High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.4

ℹ 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/typescript@4.8.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.

View full report

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Feb 1, 2026

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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by changing the version of @backstage/types. However, the proposed change of replacing workspace:^ with a fixed version 0.1.1 in packages/config/package.json is problematic for this monorepo. It breaks the internal dependency linkage, forcing @backstage/config to use an outdated version from npm while other local packages use a newer version (1.1.0) from the workspace. This can introduce type conflicts and other bugs. I've recommended reverting this change as it is incorrect for a project using Yarn workspaces.

},
"dependencies": {
"@backstage/types": "workspace:^",
"@backstage/types": "0.1.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This change from workspace:^ to a specific version 0.1.1 is incorrect for this monorepo setup. It forces this package to use an older, published version of @backstage/types from npm, while other packages in the workspace will use the local version (1.1.0 as per packages/types/package.json). This will likely lead to type inconsistencies, build failures, or runtime errors. The dependency should remain linked to the workspace version to ensure consistency across the project.

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

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This pull request updates the dependency management for the @backstage/types package in the config package. The change transitions from using a workspace protocol reference to a fixed version number (0.1.1). This modification ensures that the package will use a specific published version of the dependency rather than relying on the local workspace version. Such changes are typically made when preparing a package for publication or when standardizing dependency resolution across different deployment environments to ensure consistency and reproducibility.

Changes

File(s) Summary
packages/config/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 PM as Package Manager
    participant Config as @backstage/config
    participant Types as @backstage/types

    Note over PM,Types: Dependency Resolution Change

    rect rgb(255, 240, 240)
        Note over PM,Config: BEFORE: workspace:^ reference
        PM->>Config: Install dependencies
        Config->>PM: Request @backstage/types (workspace)
        PM->>PM: Resolve from local workspace
        PM-->>Config: Link local workspace version
    end

    rect rgb(240, 255, 240)
        Note over PM,Config: AFTER: Fixed version 0.1.1
        PM->>Config: Install dependencies
        Config->>PM: Request @backstage/types@0.1.1
        PM->>Types: Fetch from registry
        Types-->>PM: Return version 0.1.1
        PM-->>Config: Install published package
    end
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
Copy link
Copy Markdown

github-actions Bot commented Feb 8, 2026

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!

@github-actions github-actions Bot added the stale label Feb 8, 2026
@github-actions github-actions Bot closed this Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants