[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/scaffolder-backend-module-sentry/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

---

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)

---

EntelligenceAI PR Summary

Updated dependency version specifications in the Sentry scaffolder backend module from workspace references to explicit semantic versions.

• Changed @backstage/config from workspace:^ to 0.1.1
• Changed @backstage/errors from workspace:^ to 0.1.1
• Changed @backstage/plugin-scaffolder-node from workspace:^ to 0.2.0
• Transitions from dynamic workspace references to fixed version pinning for controlled dependency management

[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 updates the dependency management strategy for the Sentry scaffolder backend module by replacing workspace protocol references with explicit semantic versions. Three Backstage dependencies are affected: @backstage/config and @backstage/errors are pinned to version 0.1.1, while @backstage/plugin-scaffolder-node is pinned to version 0.2.0. This change transitions from dynamic workspace references (workspace:^) to fixed version specifications, which is typically done to prepare a package for independent publishing or to establish stricter dependency version control across the project.

Changes

File(s)	Summary
plugins/scaffolder-backend-module-sentry/package.json	Replaced workspace protocol (workspace:^) with explicit semantic versions for three Backstage dependencies: @backstage/config and @backstage/errors pinned to 0.1.1, and @backstage/plugin-scaffolder-node pinned to 0.2.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Sentry as scaffolder-backend-module-sentry
    participant Config as @backstage/config
    participant Errors as @backstage/errors
    participant Scaffolder as @backstage/plugin-scaffolder-node

    Note over Dev,Scaffolder: Dependency Version Update (workspace:^ → fixed versions)
    
    Dev->>PM: Update package.json dependencies
    activate PM
    
    Note over PM: Change workspace references to fixed versions:<br/>config: 0.1.1<br/>errors: 0.1.1<br/>scaffolder-node: 0.2.0
    
    PM->>Config: Resolve @backstage/config@0.1.1
    activate Config
    Config-->>PM: Package resolved
    deactivate Config
    
    PM->>Errors: Resolve @backstage/errors@0.1.1
    activate Errors
    Errors-->>PM: Package resolved
    deactivate Errors
    
    PM->>Scaffolder: Resolve @backstage/plugin-scaffolder-node@0.2.0
    activate Scaffolder
    Scaffolder-->>PM: Package resolved
    deactivate Scaffolder
    
    PM->>Sentry: Install dependencies
    activate Sentry
    Sentry-->>PM: Dependencies installed
    deactivate Sentry
    
    PM-->>Dev: Build ready with pinned versions
    deactivate PM

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!