Skip to content

[Snyk] Fix for 2 vulnerabilities#11885

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-65fc16a9c250c25b3ac302154648513d
Open

[Snyk] Fix for 2 vulnerabilities#11885
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-65fc16a9c250c25b3ac302154648513d

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Feb 7, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/events-backend-module-bitbucket-cloud/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
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235959
  380  
low severity Server-side Request Forgery (SSRF)
SNYK-JS-WEBPACK-15235969
  380  

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:

🦉 Server-side Request Forgery (SSRF)


EntelligenceAI PR Summary

This PR transitions the Bitbucket Cloud events backend module from workspace protocol dependencies to fixed version numbers.

  • Changed @backstage/backend-plugin-api from workspace:^ to 0.6.19
  • Changed @backstage/plugin-events-node from workspace:^ to 0.2.9
  • Modified in plugins/events-backend-module-bitbucket-cloud/package.json
  • Indicates preparation for package release or dependency management standardization

@codesandbox
Copy link

codesandbox bot commented Feb 7, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Author

snyk-io bot commented Feb 7, 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.

@socket-security
Copy link

@socket-security
Copy link

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
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/@graphql-codegen/graphql-modules-preset@3.1.2npm/@graphql-codegen/cli@3.3.0npm/@graphql-codegen/typescript@3.0.3npm/@graphql-codegen/typescript-resolvers@3.2.0npm/@babel/traverse@7.19.1

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

View full report

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates dependency management for the Bitbucket Cloud events backend module by transitioning from workspace protocol references to explicit version numbers. The changes replace workspace:^ with fixed versions for two Backstage dependencies: @backstage/backend-plugin-api (now 0.6.19) and @backstage/plugin-events-node (now 0.2.9). This modification suggests preparation for package publication or a shift toward standardized dependency versioning outside of a monorepo workspace context, ensuring consistent and reproducible builds with locked dependency versions.

Changes

File(s) Summary
plugins/events-backend-module-bitbucket-cloud/package.json Updated dependency specifications from workspace protocol (workspace:^) to explicit versions: @backstage/backend-plugin-api to 0.6.19 and @backstage/plugin-events-node to 0.2.9.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant BBC as events-backend-module-bitbucket-cloud
    participant BPA as @backstage/backend-plugin-api
    participant EPN as @backstage/plugin-events-node

    Note over PM,EPN: Dependency Resolution Flow

    PM->>BBC: Install dependencies
    
    alt Before Change (workspace:^)
        BBC->>PM: Request workspace version of backend-plugin-api
        PM->>BPA: Resolve from local workspace
        BBC->>PM: Request workspace version of plugin-events-node
        PM->>EPN: Resolve from local workspace
    else After Change (pinned versions)
        BBC->>PM: Request backend-plugin-api@0.6.19
        PM->>BPA: Resolve specific version 0.6.19
        BBC->>PM: Request plugin-events-node@0.2.9
        PM->>EPN: Resolve specific version 0.2.9
    end

    BPA-->>BBC: Provide API interfaces
    EPN-->>BBC: Provide event handling capabilities
    
    Note over BBC: Module ready with pinned dependencies
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants