[Snyk] Fix for 7 vulnerabilities

[q1blue]

Snyk has created this PR to fix 7 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
	Symlink Attack SNYK-JS-BACKSTAGEPLUGINSCAFFOLDERNODE-15054276	258
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	210
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	113
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Prototype Pollution SNYK-JS-LODASHES-15053836	88
	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:

🦉 Symlink Attack
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

Updated dependency version specifications in the scaffolder-backend-module-gitlab plugin from workspace protocol to explicit versions.

• Pinned @backstage/config to version 0.1.1
• Pinned @backstage/errors to version 0.1.1
• Pinned @backstage/integration to version 0.1.0
• Pinned @backstage/plugin-scaffolder-node to version 0.11.2
• Transitioned from monorepo workspace dependencies (workspace:^) to fixed version dependencies
• Changes made in plugins/scaffolder-backend-module-gitlab/package.json

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! 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 aims to bolster the project's security by upgrading several @backstage dependencies within the scaffolder-backend-module-gitlab plugin. The updates target and resolve seven distinct security vulnerabilities, enhancing the overall robustness and safety of the application against known exploits. While the package.json has been updated, a manual step is required to synchronize the yarn.lock file.

Highlights

• Vulnerability Remediation: This pull request, automatically generated by Snyk, addresses 7 identified security vulnerabilities within the project's yarn dependencies, including high-severity Symlink Attacks and various medium-severity issues like Prototype Pollution and Regular Expression Denial of Service.
• Dependency Version Updates: Key @backstage dependencies, specifically @backstage/config, @backstage/errors, @backstage/integration, and @backstage/plugin-scaffolder-node, have been updated to specific, newer versions in plugins/scaffolder-backend-module-gitlab/package.json to incorporate security fixes.
• Manual yarn.lock Update Required: A warning is present indicating that the yarn.lock file was not automatically updated by Snyk and requires manual intervention. This is particularly important for projects utilizing Yarn's zero-install feature to ensure consistency and proper 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]

✅ 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]

Walkthrough

This pull request updates the dependency management strategy for the scaffolder-backend-module-gitlab plugin by replacing workspace protocol references with explicit version numbers. Four Backstage packages are affected: @backstage/config and @backstage/errors are pinned to version 0.1.1, @backstage/integration to version 0.1.0, and @backstage/plugin-scaffolder-node to version 0.11.2. This change transitions the package from using monorepo workspace dependencies (workspace:^) to fixed version dependencies, which typically indicates preparation for independent package publication or the establishment of more explicit version control and dependency management.

Changes

File(s)	Summary
plugins/scaffolder-backend-module-gitlab/package.json	Replaced workspace protocol references (workspace:^) with explicit version numbers for four Backstage dependencies: @backstage/config (0.1.1), @backstage/errors (0.1.1), @backstage/integration (0.1.0), and @backstage/plugin-scaffolder-node (0.11.2).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Deps as Dependencies
    
    Note over Dev,Deps: Dependency Version Update Process
    
    Dev->>PM: Update package.json dependencies
    Note right of Dev: Change workspace:^ to fixed versions:<br/>- @backstage/config: 0.1.1<br/>- @backstage/errors: 0.1.1<br/>- @backstage/integration: 0.1.0<br/>- @backstage/plugin-scaffolder-node: 0.11.2
    
    PM->>Deps: Resolve dependency versions
    Deps-->>PM: Return resolved packages
    PM-->>Dev: Dependencies updated successfully
    
    Note over Dev,Deps: No runtime behavior changes<br/>Only dependency version pinning

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.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix several vulnerabilities by updating dependencies. However, the proposed changes are incorrect for this monorepo setup. It replaces workspace: dependencies with pinned versions from the public registry, causing significant downgrades for several key packages (@backstage/config, @backstage/errors, @backstage/integration). This will likely break the project. The changes should be reverted. The PR also notes that yarn.lock was not updated, which is another indication that the automated process failed. The vulnerabilities should be addressed by other means, such as using yarn's resolutions feature in the root package.json.

[gemini-code-assist]

These dependency changes introduced by Snyk are incorrect and will likely break the project. The workspace:^ protocol is essential in this monorepo to ensure that packages use the versions from the local workspace. Replacing them with pinned versions from the public registry breaks this model.

Specifically, this change introduces major version downgrades for several packages:

• @backstage/config: 1.0.8 (in workspace) -> 0.1.1
• @backstage/errors: 1.2.1 (in workspace) -> 0.1.1
• @backstage/integration: 1.5.1 (in workspace) -> 0.1.0

Such drastic downgrades will almost certainly lead to build failures or runtime errors due to API incompatibilities.

It's recommended to revert these changes. To fix the underlying security vulnerabilities, consider using Yarn's resolutions field in the root package.json to force a secure version of the transitive dependency that has the vulnerability.

    "@backstage/config": "workspace:^",
    "@backstage/errors": "workspace:^",
    "@backstage/integration": "workspace:^",
    "@backstage/plugin-scaffolder-node": "workspace:^"