[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/todo-backend/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-15127355	127
	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

Updated todo-backend plugin dependencies from workspace protocol to pinned versions for standalone distribution compatibility.

• Changed @backstage/backend-common from workspace:^ to version 0.24.1
• Changed @backstage/catalog-client from workspace:^ to version 0.2.0
• Changed @backstage/catalog-model from workspace:^ to version 0.1.1
• Changed @backstage/plugin-catalog-node from workspace:^ to version 1.0.0
• Enables version consistency and prepares plugin for potential standalone distribution

[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, automatically generated by Snyk, aims to enhance the security posture of the project by resolving critical vulnerabilities. It achieves this by updating specific Backstage dependencies within the plugins/todo-backend package to their patched versions. The changes are confined to the package.json file, ensuring that the project benefits from the latest security fixes provided by the updated libraries.

Highlights

• Vulnerability Fixes: This pull request addresses two security vulnerabilities: a 'Directory Traversal' (SNYK-JS-TAR-15127355) and an 'Uncontrolled Recursion' (SNYK-JS-ESLINT-15102420) by updating several Backstage dependencies.
• Dependency Updates: The plugins/todo-backend/package.json file has been updated to specify exact versions for @backstage/backend-common (0.24.1), @backstage/catalog-client (0.2.0), @backstage/catalog-model (0.1.1), and @backstage/plugin-catalog-node (1.0.0), moving away from workspace:^ references.
• Yarn Zero-Install Note: Users leveraging Yarn's zero-install feature should be aware that the .yarn/cache/ directory is not updated by this PR and will require a manual yarn command to synchronize.
• Yarn.lock Warning: A warning is present indicating that yarn.lock failed to update and requires manual intervention before merging.

Changelog

• plugins/todo-backend/package.json
  • Updated @backstage/backend-common from workspace:^ to 0.24.1.
  • Updated @backstage/catalog-client from workspace:^ to 0.2.0.
  • Updated @backstage/catalog-model from workspace:^ to 0.1.1.
  • Updated @backstage/plugin-catalog-node from workspace:^ to 1.0.0.

Activity

• This pull request was automatically created by Snyk to address identified vulnerabilities.
• The PR description includes details about the vulnerabilities fixed, the affected files, and specific instructions for Yarn zero-install users.
• A warning regarding the failure to update yarn.lock is present, indicating a manual step is required.

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 failed. 1 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	0	1	0	1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm atob under CC-BY-3.0 License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS) From: ? → npm/atob@2.1.2 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/atob@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the todo-backend plugin by replacing workspace protocol references with specific pinned versions. Four Backstage dependencies are affected: backend-common (0.24.1), catalog-client (0.2.0), catalog-model (0.1.1), and plugin-catalog-node (1.0.0). This transition from monorepo workspace dependencies to explicit published package versions suggests preparation for standalone plugin distribution or enforcement of version consistency across different deployment environments. The change ensures reproducible builds and eliminates reliance on workspace-specific dependency resolution.

Changes

File(s)	Summary
plugins/todo-backend/package.json	Replaced workspace protocol (workspace:^) with pinned versions for four Backstage dependencies: @backstage/backend-common (0.24.1), @backstage/catalog-client (0.2.0), @backstage/catalog-model (0.1.1), and @backstage/plugin-catalog-node (1.0.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant TB as todo-backend Plugin
    participant BC as @backstage/backend-common
    participant CC as @backstage/catalog-client
    participant CM as @backstage/catalog-model
    participant CN as @backstage/plugin-catalog-node

    Note over Dev,CN: Dependency Version Pinning Update

    Dev->>PM: Update package.json dependencies
    Note right of PM: Change workspace:^ to<br/>specific versions

    PM->>TB: Install dependencies
    
    TB->>BC: Require v0.24.1 (pinned)
    Note right of BC: Previously: workspace:^
    BC-->>TB: Backend utilities available
    
    TB->>CC: Require v0.2.0 (pinned)
    Note right of CC: Previously: workspace:^
    CC-->>TB: Catalog client available
    
    TB->>CM: Require v0.1.1 (pinned)
    Note right of CM: Previously: workspace:^
    CM-->>TB: Catalog models available
    
    TB->>CN: Require v1.0.0 (pinned)
    Note right of CN: Previously: workspace:^
    CN-->>TB: Catalog node utilities available

    PM-->>Dev: Dependencies resolved and installed
    
    Note over Dev,CN: All dependencies now use<br/>fixed versions instead of<br/>workspace references

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 updates the plugins/todo-backend/package.json file, specifically changing several @backstage dependency versions from workspace:^ to fixed versions. Affected dependencies include @backstage/backend-common (to 0.24.1), @backstage/catalog-client (to 0.2.0), @backstage/catalog-model (to 0.1.1), and @backstage/plugin-catalog-node (to 1.0.0). There are no review comments provided for this change.