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/scaffolder-backend-module-gitlab/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 transitions the scaffolder-backend-module-gitlab plugin from workspace dependencies to fixed package versions for release preparation.

  • Changed @backstage/config from workspace:^ to version 0.1.1
  • Changed @backstage/integration from workspace:^ to version 0.1.0
  • Changed @backstage/plugin-scaffolder-node from workspace:^ to version 0.2.0
  • Indicates preparation for package publishing outside monorepo workspace

@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 is an automated security fix initiated by Snyk, aiming to patch critical vulnerabilities within the project's dependencies. It primarily involves updating specific package versions to their secure counterparts, thereby enhancing the overall security posture of the application. The changes are focused on a single package.json file, reflecting a targeted effort to mitigate known risks.

Highlights

  • Vulnerability Fixes: This pull request, automatically generated by Snyk, addresses three medium-severity vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
  • Dependency Upgrades: To resolve the identified vulnerabilities, the following dependencies in plugins/scaffolder-backend-module-gitlab/package.json have been upgraded: @backstage/config from workspace:^ to 0.1.1, @backstage/integration from workspace:^ to 0.1.0, and @backstage/plugin-scaffolder-node from workspace:^ to 0.2.0.
  • Yarn Zero-Installs Note: Users employing Yarn's zero-installs feature should be aware that this PR does not update the .yarn/cache/ directory. A manual yarn command will be required to update the cache after merging.
  • Manual yarn.lock Update Required: Snyk reported a failure to update yarn.lock, indicating that this file will need to be manually updated before merging this pull request to ensure consistency and correct dependency resolution.
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

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.

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management strategy for the scaffolder-backend-module-gitlab plugin by replacing workspace protocol references with fixed version numbers. Three Backstage packages are affected: @backstage/config (now pinned to 0.1.1), @backstage/integration (pinned to 0.1.0), and @backstage/plugin-scaffolder-node (pinned to 0.2.0). This transition from workspace:^ to explicit version numbers suggests the package is being prepared for independent publication or release outside of the monorepo workspace environment, ensuring consumers receive specific, tested versions of dependencies rather than workspace-relative references.

Changes

File(s) Summary
plugins/scaffolder-backend-module-gitlab/package.json Updated three Backstage dependencies from workspace protocol (workspace:^) to fixed versions: @backstage/config to 0.1.1, @backstage/integration to 0.1.0, and @backstage/plugin-scaffolder-node to 0.2.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    participant Plugin as scaffolder-backend-module-gitlab

    Dev->>PM: Update package.json dependencies
    Note over Dev,PM: Pin versions:<br/>config: 0.1.1<br/>integration: 0.1.0<br/>scaffolder-node: 0.2.0
    
    Dev->>PM: Run install command
    PM->>Registry: Request @backstage/config@0.1.1
    Registry-->>PM: Return package
    PM->>Registry: Request @backstage/integration@0.1.0
    Registry-->>PM: Return package
    PM->>Registry: Request @backstage/plugin-scaffolder-node@0.2.0
    Registry-->>PM: Return package
    
    PM->>Plugin: Install pinned dependencies
    Note over Plugin: Dependencies locked to<br/>specific versions
    PM-->>Dev: Installation complete
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.

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 updates several dependency versions in plugins/scaffolder-backend-module-gitlab/package.json to address reported vulnerabilities. While the dependency updates are correctly applied in package.json, the pull request description indicates that the yarn.lock file failed to update. It is critical to manually update yarn.lock to ensure these fixes are applied consistently and reproducibly.

Comment on lines +34 to +37
"@backstage/config": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/plugin-scaffolder-node": "workspace:^",
"@backstage/integration": "0.1.0",
"@backstage/plugin-scaffolder-node": "0.2.0",

Choose a reason for hiding this comment

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

critical

The pull request description notes that yarn.lock failed to update. It is crucial that yarn.lock is manually updated to reflect these dependency changes. Without an updated yarn.lock, the project might still be vulnerable, or builds could become inconsistent due to differing dependency resolutions. This manual update is required before merging.

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.

3 participants