Skip to content

[Snyk] Fix for 1 vulnerabilities#10801

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-4bcdad57a8f7ba099c3baf148cf0a94a
Closed

[Snyk] Fix for 1 vulnerabilities#10801
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-4bcdad57a8f7ba099c3baf148cf0a94a

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jan 26, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/kubernetes-backend/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
  575  

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

Updates dependency version specifications in the kubernetes-backend plugin to use pinned versions instead of workspace references.

  • Changed @backstage/catalog-model, @backstage/plugin-auth-node, @backstage/plugin-catalog-node, @backstage/plugin-kubernetes-common, and @backstage/plugin-permission-node from workspace:^ to specific pinned versions
  • Upgraded @kubernetes/client-node external dependency from 0.18.1 to 0.21.0
  • Improves dependency stability and version control for the kubernetes-backend plugin

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 26, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@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

@entelligence-ai-pr-reviews entelligence-ai-pr-reviews Bot left a comment

Choose a reason for hiding this comment

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

Walkthrough

This PR updates dependency management in the kubernetes-backend plugin by transitioning from workspace protocol references to pinned versions for internal Backstage dependencies. Five internal packages (@backstage/catalog-model, @backstage/plugin-auth-node, @backstage/plugin-catalog-node, @backstage/plugin-kubernetes-common, and @backstage/plugin-permission-node) are locked to specific versions ranging from 0.1.0 to 1.0.0. Additionally, the external @kubernetes/client-node dependency is upgraded from version 0.18.1 to 0.21.0. These changes likely aim to improve stability and ensure compatibility by locking dependencies to specific versions rather than using workspace references.

Changes

File(s) Summary
plugins/kubernetes-backend/package.json Updated five Backstage internal dependencies from workspace protocol references (workspace:^) to pinned versions (0.1.0-1.0.0), and upgraded @kubernetes/client-node from 0.18.1 to 0.21.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as kubernetes-backend/package.json
    participant NPM as Package Manager
    participant Deps as Dependencies

    Dev->>PKG: Update dependency versions
    Note over PKG: Pin versions:<br/>- catalog-model: 0.1.1<br/>- plugin-auth-node: 0.1.0<br/>- plugin-catalog-node: 1.0.0<br/>- plugin-kubernetes-common: 0.1.0<br/>- plugin-permission-node: 0.1.0<br/>- @kubernetes/client-node: 0.18.1→0.21.0
    
    Dev->>NPM: Run package install
    NPM->>Deps: Resolve dependencies
    
    alt Version conflicts detected
        Deps-->>NPM: Report conflicts
        NPM-->>Dev: Installation fails
    else All versions compatible
        Deps-->>NPM: Dependencies resolved
        NPM->>NPM: Download packages
        NPM->>NPM: Install to node_modules
        NPM-->>Dev: Installation successful
    end
    
    Note over Dev,Deps: kubernetes-backend now uses<br/>pinned versions instead of<br/>workspace references
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.

Comment on lines +59 to 68
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration-aws-node": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-kubernetes-common": "workspace:^",
"@backstage/plugin-auth-node": "0.1.0",
"@backstage/plugin-catalog-node": "1.0.0",
"@backstage/plugin-kubernetes-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-permission-node": "0.1.0",
"@google-cloud/container": "^4.0.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.

Correctness: Revert internal dependencies (e.g., @backstage/catalog-model) to workspace:^. Hardcoding versions breaks local workspace linking, forcing the build to use published artifacts instead of local source code.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

File: plugins/kubernetes-backend/package.json
Lines: 59-68

Problem: Internal Backstage dependencies were changed from `workspace:^` protocol to hardcoded version numbers. This breaks the monorepo workspace linking mechanism.

Fix Required:
1. Revert the following dependencies back to `workspace:^`:
   - @backstage/catalog-model (currently 0.1.1)
   - @backstage/plugin-auth-node (currently 0.1.0)
   - @backstage/plugin-catalog-node (currently 1.0.0)
   - @backstage/plugin-kubernetes-common (currently 0.1.0)
   - @backstage/plugin-permission-node (currently 0.1.0)

2. Keep the @kubernetes/client-node upgrade to 0.21.0 as this is an external dependency.

3. Verify no other package.json files in the monorepo have similar accidental version pinning.

Expected result: All @backstage/* dependencies should use `workspace:^` to maintain proper monorepo workspace resolution.
✨ Committable Code Suggestion

💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.

Suggested change
"@backstage/catalog-model": "0.1.1",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration-aws-node": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-kubernetes-common": "workspace:^",
"@backstage/plugin-auth-node": "0.1.0",
"@backstage/plugin-catalog-node": "1.0.0",
"@backstage/plugin-kubernetes-common": "0.1.0",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-permission-node": "0.1.0",
"@google-cloud/container": "^4.0.0",
"@azure/identity": "^3.2.1",
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/integration-aws-node": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-catalog-node": "workspace:^",
"@backstage/plugin-kubernetes-common": "workspace:^",
"@backstage/plugin-permission-common": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@google-cloud/container": "^4.0.0",
"@jest-mock/express": "^2.0.1",
"@kubernetes/client-node": "0.21.0",
"@types/express": "^4.17.6",
"@types/luxon": "^3.0.0",
"compression": "^1.7.4",

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 2, 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 2, 2026
@github-actions github-actions Bot closed this Mar 28, 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.

0 participants