Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Jan 31, 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):

  • plugins/airbrake-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
  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 Backstage dependencies to specific versions in the airbrake-backend plugin, replacing workspace protocol references.

  • Updated @backstage/backend-common from workspace:^ to fixed version 0.24.1
  • Updated @backstage/config from workspace:^ to fixed version 0.1.1
  • Changes made in plugins/airbrake-backend/package.json
  • Indicates transition from monorepo workspace dependencies to published package versions

@codesandbox
Copy link

codesandbox bot commented Jan 31, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

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 project's security posture by resolving three identified vulnerabilities within the plugins/airbrake-backend module. The changes involve specific dependency version bumps in package.json to mitigate risks such as Directory Traversal and Uncontrolled Recursion.

Highlights

  • Security Vulnerability Fixes: This PR addresses three security vulnerabilities: two instances of "Directory Traversal" (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one "Uncontrolled Recursion" (SNYK-JS-ESLINT-15102420).
  • Dependency Updates: The fix involves updating @backstage/backend-common to 0.24.1 and @backstage/config to 0.1.1 within plugins/airbrake-backend/package.json.
  • Manual yarn.lock Update Required: The automated process failed to update yarn.lock, which will require manual intervention before merging.
  • Zero-Install Warning: Users leveraging Yarn's zero-installs feature are advised to run yarn to update the .yarn/cache/ directory after pulling these changes.
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

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

snyk-io bot commented Jan 31, 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

@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 three security vulnerabilities by updating dependencies in plugins/airbrake-backend/package.json. While the intent is good, the proposed changes have a critical issue.

The dependency @backstage/config is being downgraded to version 0.1.1, which is a very old version and highly likely to be incompatible with the rest of your codebase, potentially causing build failures or runtime errors. I've left a comment with a suggestion to revert this specific change.

Additionally, the PR changes dependencies from using the local workspace:^ version to a pinned version from the public registry. This can be a valid strategy for a quick security fix, but it deviates from the monorepo's dependency management and can introduce maintenance challenges.

Finally, as noted in the PR description, yarn.lock has not been updated. This is a critical step that must be performed manually to ensure the dependency changes are correctly applied and to resolve the transitive dependencies to their patched versions. Please ensure you run yarn install and commit the updated yarn.lock file after addressing the feedback.

Comment on lines +25 to +27
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config": "0.1.1",

Choose a reason for hiding this comment

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

critical

This automated Snyk PR makes two significant changes to dependencies that need careful review:

  1. @backstage/config downgrade (Critical): The change from "workspace:^" to "0.1.1" is a massive downgrade from the workspace version (likely 1.0.8 or newer). This is almost certainly an error by the Snyk bot and will likely cause build failures or runtime errors due to API incompatibilities with other @backstage packages. This change should be reverted.

  2. Dependency Pinning (Maintainability): Both @backstage/backend-common and @backstage/config are being changed from workspace:^ to pinned versions. This breaks the monorepo's convention of using local workspace packages. While pinning @backstage/backend-common to 0.24.1 might be a valid short-term fix for the tar vulnerability, this approach can create maintenance issues in the long run. The ideal solution would be to update the workspace version of @backstage/backend-common itself.

Given the critical nature of the @backstage/config downgrade, I suggest rejecting that specific change. You should investigate the eslint vulnerability (SNYK-JS-ESLINT-15102420) separately; the fix may lie in updating a devDependency in the root of the repository rather than here.

    "@backstage/backend-common": "0.24.1",
    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/config": "workspace:^"

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management strategy for the airbrake-backend plugin by replacing workspace protocol references with fixed version numbers. Specifically, two Backstage dependencies are pinned to explicit versions: @backstage/backend-common is set to version 0.24.1 and @backstage/config is set to version 0.1.1. This change transitions from using monorepo workspace dependencies (indicated by workspace:^) to published package versions, which typically occurs when preparing a package for independent publication or when moving away from a monorepo structure.

Changes

File(s) Summary
plugins/airbrake-backend/package.json Replaced workspace protocol references with fixed versions for two dependencies: @backstage/backend-common changed from workspace:^ to 0.24.1 and @backstage/config changed from workspace:^ to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Build as Build System
    participant AirbrakePlugin as Airbrake Backend Plugin
    participant BackendCommon as @backstage/backend-common
    participant Config as @backstage/config
    participant NPM as NPM Registry

    Note over Dev,NPM: Dependency Resolution Change: Workspace → Fixed Versions

    Dev->>Build: Run package installation
    Build->>AirbrakePlugin: Read package.json dependencies
    
    Note over AirbrakePlugin: Dependencies now pinned:<br/>backend-common: 0.24.1<br/>config: 0.1.1
    
    AirbrakePlugin->>Build: Request @backstage/backend-common@0.24.1
    AirbrakePlugin->>Build: Request @backstage/config@0.1.1
    
    Build->>NPM: Fetch @backstage/backend-common@0.24.1
    NPM-->>Build: Return package
    
    Build->>NPM: Fetch @backstage/config@0.1.1
    NPM-->>Build: Return package
    
    Build->>AirbrakePlugin: Install dependencies
    
    Note over AirbrakePlugin,Config: Plugin now uses fixed versions<br/>instead of workspace references
    
    AirbrakePlugin->>BackendCommon: Import backend utilities
    AirbrakePlugin->>Config: Import configuration types
    
    Note over Dev,NPM: Result: Plugin can be published<br/>independently with stable 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.

3 participants