Skip to content

[Snyk] Fix for 6 vulnerabilities#10451

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

[Snyk] Fix for 6 vulnerabilities#10451
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-1fe066e3f85da70b6bbf94051c22fd9f

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Jan 22, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/techdocs-cli-embedded-app/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 Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  210  
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  146  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  113  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  88  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  88  
medium severity 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 converts workspace protocol dependencies to fixed version numbers for the techdocs-cli-embedded-app package.

  • Pinned @backstage/core-app-api to version 0.1.0
  • Pinned @backstage/core-components to version 0.1.0
  • Pinned @backstage/integration-react to version 0.1.1
  • Pinned @backstage/plugin-techdocs to version 0.1.1
  • Pinned @backstage/plugin-techdocs-react to version 0.1.0
  • Enables standalone distribution and dependency version locking

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 22, 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, automatically generated by Snyk, aims to enhance the security posture of the application by upgrading specific @backstage package dependencies. The updates target and resolve a set of 6 identified vulnerabilities, ensuring the project benefits from the latest security patches. Reviewers should pay attention to the manual yarn.lock update requirement.

Highlights

  • Vulnerability Fixes: This pull request addresses and fixes 6 identified security vulnerabilities within the project's yarn dependencies, as detected by Snyk.
  • Dependency Updates: Several @backstage dependencies in packages/techdocs-cli-embedded-app/package.json have been updated from workspace:^ to specific version numbers to resolve the vulnerabilities.
  • Manual yarn.lock Update Required: A warning is noted that the yarn.lock file was not automatically updated and requires manual intervention, especially 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.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Jan 22, 2026

Snyk checks have failed. 2 issues have been found so far.

Status Scanner Critical High Medium Low Total (2)
Open Source Security 0 0 2 0 2 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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

Warn High
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/@storybook/addon-controls@6.5.16npm/@storybook/builder-webpack5@6.5.16npm/@storybook/manager-webpack5@6.5.16npm/@storybook/react@6.5.16npm/caniuse-lite@1.0.30001378

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

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 several vulnerabilities by changing dependency versions in packages/techdocs-cli-embedded-app/package.json. However, the proposed changes are fundamentally flawed. They replace workspace:^ specifiers with very old, pinned versions of @backstage packages. This constitutes a major version downgrade that will almost certainly break the application and disrupt the monorepo's local development workflow. The correct approach is to update dependencies to newer versions or use Yarn's resolutions feature to target the vulnerable transitive dependencies directly. Furthermore, as noted in the pull request description, the yarn.lock file has not been updated, which is a required step for any dependency change. This pull request should not be merged in its current state and the vulnerabilities should be addressed manually.

Comment on lines +14 to +20
"@backstage/core-app-api": "0.1.0",
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
"@backstage/plugin-catalog": "workspace:^",
"@backstage/plugin-techdocs": "workspace:^",
"@backstage/plugin-techdocs-react": "workspace:^",
"@backstage/plugin-techdocs": "0.1.1",
"@backstage/plugin-techdocs-react": "0.1.0",
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

These dependency changes represent a significant downgrade and will likely break the application. The versions are being pinned to very old releases (e.g., 0.1.0 for @backstage/core-app-api when newer 1.x versions exist in the repository), and the workspace:^ protocol is being removed, which is essential for monorepo development.

This approach to fixing vulnerabilities is incorrect and harmful. Instead of downgrading, consider using Yarn's resolutions field in the root package.json to force newer, non-vulnerable versions of the transitive dependencies. For example:

"resolutions": {
  "lodash": "^4.17.21",
  "tar": "^6.1.11"
}

These changes should be reverted, and a proper dependency resolution strategy should be applied manually.

Suggested change
"@backstage/core-app-api": "0.1.0",
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/integration-react": "0.1.1",
"@backstage/plugin-catalog": "workspace:^",
"@backstage/plugin-techdocs": "workspace:^",
"@backstage/plugin-techdocs-react": "workspace:^",
"@backstage/plugin-techdocs": "0.1.1",
"@backstage/plugin-techdocs-react": "0.1.0",
"@backstage/core-app-api": "workspace:^",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/integration-react": "workspace:^",
"@backstage/plugin-catalog": "workspace:^",
"@backstage/plugin-techdocs": "workspace:^",
"@backstage/plugin-techdocs-react": "workspace:^",

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

Walkthrough

This pull request updates the dependency management strategy for the techdocs-cli-embedded-app package by replacing workspace protocol references with fixed version numbers for five Backstage packages. The changes pin @backstage/core-app-api and @backstage/core-components to version 0.1.0, @backstage/integration-react to 0.1.1, @backstage/plugin-techdocs to 0.1.1, and @backstage/plugin-techdocs-react to 0.1.0. This transition from local workspace dependencies to specific published npm package versions indicates preparation for standalone distribution or a move to lock dependencies at stable versions for improved version control and reproducibility.

Changes

File(s) Summary
packages/techdocs-cli-embedded-app/package.json Converted five Backstage package dependencies from workspace protocol references to fixed version numbers: @backstage/core-app-api (0.1.0), @backstage/core-components (0.1.0), @backstage/integration-react (0.1.1), @backstage/plugin-techdocs (0.1.1), and @backstage/plugin-techdocs-react (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as techdocs-cli-embedded-app
    participant WS as Workspace Packages
    participant NPM as NPM Registry

    Note over Dev,NPM: Dependency Version Update Process

    Dev->>PKG: Update package.json dependencies
    
    rect rgb(255, 240, 240)
        Note over PKG,WS: Before: Using workspace references
        PKG->>WS: Depends on workspace:^ versions
        Note over WS: @backstage/core-app-api<br/>@backstage/core-components<br/>@backstage/integration-react<br/>@backstage/plugin-techdocs<br/>@backstage/plugin-techdocs-react
    end
    
    rect rgb(240, 255, 240)
        Note over PKG,NPM: After: Using published versions
        PKG->>NPM: Depends on specific versions
        Note over NPM: @backstage/core-app-api: 0.1.0<br/>@backstage/core-components: 0.1.0<br/>@backstage/integration-react: 0.1.1<br/>@backstage/plugin-techdocs: 0.1.1<br/>@backstage/plugin-techdocs-react: 0.1.0
    end
    
    Dev->>PKG: Run npm/yarn install
    PKG->>NPM: Fetch published packages
    NPM-->>PKG: Return versioned packages
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

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 Jan 29, 2026
@github-actions github-actions Bot closed this Apr 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants