[Snyk] Fix for 2 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	685
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	590

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR converts workspace protocol dependencies to fixed versions in the scaffolder-backend-module-gitlab plugin to prepare it for npm publication.

• 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
• Enables proper dependency resolution from npm registry for package consumers

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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 PR prepares the scaffolder-backend-module-gitlab plugin for publication by replacing workspace protocol dependencies with fixed version numbers. The change converts three Backstage package dependencies from monorepo workspace references (workspace:^) to specific npm registry versions. This ensures that when the package is published, consumers can properly resolve dependencies from the public npm registry rather than relying on internal workspace references. The affected packages are @backstage/config (0.1.1), @backstage/integration (0.1.0), and @backstage/plugin-scaffolder-node (0.2.0).

Changes

File(s)	Summary
plugins/scaffolder-backend-module-gitlab/package.json	Converted 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 Build as Build System
    participant Plugin as scaffolder-backend-module-gitlab
    participant Config as @backstage/config
    participant Integration as @backstage/integration
    participant Scaffolder as @backstage/plugin-scaffolder-node
    
    Note over Build,Scaffolder: Dependency Resolution During Build
    
    Build->>Plugin: Install dependencies
    activate Plugin
    
    Plugin->>Config: Require @backstage/config v0.1.1
    Note right of Config: Changed from workspace:^ to 0.1.1
    Config-->>Plugin: Provide config utilities
    
    Plugin->>Integration: Require @backstage/integration v0.1.0
    Note right of Integration: Changed from workspace:^ to 0.1.0
    Integration-->>Plugin: Provide integration utilities
    
    Plugin->>Scaffolder: Require @backstage/plugin-scaffolder-node v0.2.0
    Note right of Scaffolder: Changed from workspace:^ to 0.2.0
    Scaffolder-->>Plugin: Provide scaffolder utilities
    
    deactivate Plugin
    Plugin-->>Build: Dependencies resolved
    
    Note over Build,Scaffolder: No runtime behavior changes - only 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.

[github-actions]

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!