[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-cookiecutter/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
	Directory Traversal SNYK-JS-TAR-15032660	575

---

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 scaffolder-backend-module-cookiecutter plugin, replacing workspace protocol references.

• Changed @backstage/backend-common from workspace protocol to version 0.24.1
• Changed @backstage/plugin-scaffolder-backend from workspace protocol to version 2.1.0
• Changed @backstage/plugin-scaffolder-node from workspace protocol to version 0.2.0
• Improves dependency stability and prepares package for potential independent publication

[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 pull request updates the dependency management strategy for the scaffolder-backend-module-cookiecutter plugin by transitioning from workspace protocol references to explicit version pinning. Three core Backstage dependencies are now locked to specific versions: backend-common at 0.24.1, plugin-scaffolder-backend at 2.1.0, and plugin-scaffolder-node at 0.2.0. This change moves away from workspace-relative versioning to establish more predictable dependency resolution, which is typically done to improve stability, ensure reproducible builds, or prepare the package for independent publication to a package registry.

Changes

File(s)	Summary
plugins/scaffolder-backend-module-cookiecutter/package.json	Updated three Backstage dependencies from workspace protocol to explicit versions: @backstage/backend-common to 0.24.1, @backstage/plugin-scaffolder-backend to 2.1.0, and @backstage/plugin-scaffolder-node to 0.2.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant User
    participant ScaffolderBackend as Scaffolder Backend<br/>(v2.1.0)
    participant CookiecutterModule as Cookiecutter Module
    participant ScaffolderNode as Scaffolder Node<br/>(v0.2.0)
    participant BackendCommon as Backend Common<br/>(v0.24.1)

    Note over CookiecutterModule: Dependency versions pinned<br/>from workspace to specific versions

    User->>ScaffolderBackend: Request template scaffolding
    ScaffolderBackend->>CookiecutterModule: Execute cookiecutter action
    activate CookiecutterModule
    
    CookiecutterModule->>ScaffolderNode: Use scaffolder utilities
    ScaffolderNode-->>CookiecutterModule: Provide node helpers
    
    CookiecutterModule->>BackendCommon: Use common backend services
    BackendCommon-->>CookiecutterModule: Provide logging, config, etc.
    
    CookiecutterModule->>CookiecutterModule: Run cookiecutter template
    
    CookiecutterModule-->>ScaffolderBackend: Return scaffolded output
    deactivate CookiecutterModule
    ScaffolderBackend-->>User: Template generated
    
    Note over ScaffolderBackend,BackendCommon: No functional changes<br/>Only dependency version updates

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!