[Snyk] Fix for 3 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/catalog-backend-module-ldap/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	149
	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

This PR transitions the LDAP catalog backend module from workspace-based dependency management to pinned external package versions.

• Replaced workspace:^ protocol with explicit version 0.6.1 for @backstage/backend-tasks
• Replaced workspace:^ protocol with explicit version 0.1.1 for @backstage/catalog-model
• Replaced workspace:^ protocol with explicit version 0.1.0 for @backstage/plugin-catalog-common
• Replaced workspace:^ protocol with explicit version 1.0.0 for @backstage/plugin-catalog-node
• Changes made in plugins/catalog-backend-module-ldap/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, automatically generated by Snyk, aims to enhance the security posture of the project by upgrading key @backstage dependencies within the plugins/catalog-backend-module-ldap module. These dependency updates are crucial for resolving identified medium-severity vulnerabilities, specifically addressing Directory Traversal and Uncontrolled Recursion issues.

Highlights

• Dependency Upgrades: Several @backstage dependencies in plugins/catalog-backend-module-ldap/package.json have been updated from workspace:^ to specific versions (0.6.1, 0.1.1, 0.1.0, 1.0.0).
• Vulnerability Fixes: This PR addresses three medium-severity vulnerabilities: two Directory Traversal issues (SNYK-JS-TAR-15032660, SNYK-JS-TAR-15127355) and one Uncontrolled Recursion issue (SNYK-JS-ESLINT-15102420).
• Yarn Lock Warning: The yarn.lock file was not automatically updated, requiring manual intervention for zero-install users.

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.

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the LDAP catalog backend module by replacing workspace protocol references with explicit version numbers. Four Backstage packages are affected: backend-tasks (0.6.1), catalog-model (0.1.1), plugin-catalog-common (0.1.0), and plugin-catalog-node (1.0.0). This transition from workspace:^ to pinned versions suggests preparation for independent plugin distribution or a move to ensure version stability outside of a monorepo workspace environment. The change affects only the package.json file and maintains compatibility with the existing codebase while establishing explicit version dependencies.

Changes

File(s)	Summary
plugins/catalog-backend-module-ldap/package.json	Updated four Backstage package dependencies from workspace protocol references (workspace:^) to explicit version numbers: @backstage/backend-tasks to 0.6.1, @backstage/catalog-model to 0.1.1, @backstage/plugin-catalog-common to 0.1.0, and @backstage/plugin-catalog-node to 1.0.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant LDAP as catalog-backend-module-ldap
    participant BT as @backstage/backend-tasks v0.6.1
    participant CM as @backstage/catalog-model v0.1.1
    participant CC as @backstage/plugin-catalog-common v0.1.0
    participant CN as @backstage/plugin-catalog-node v1.0.0
    
    Note over Build,CN: Dependency Resolution During Build
    
    Build->>LDAP: Install dependencies
    activate LDAP
    
    LDAP->>BT: Resolve backend-tasks (now pinned to 0.6.1)
    BT-->>LDAP: Package installed
    
    LDAP->>CM: Resolve catalog-model (now pinned to 0.1.1)
    CM-->>LDAP: Package installed
    
    LDAP->>CC: Resolve catalog-common (now pinned to 0.1.0)
    CC-->>LDAP: Package installed
    
    LDAP->>CN: Resolve catalog-node (now pinned to 1.0.0)
    CN-->>LDAP: Package installed
    
    deactivate LDAP
    
    Note over Build,CN: Changed from workspace references to fixed versions

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 three vulnerabilities by changing dependency versions in plugins/catalog-backend-module-ldap/package.json. However, the proposed changes are incorrect and will likely break the project. The PR replaces workspace:^ dependencies with pinned, and in most cases, severely outdated versions from the public registry. This goes against the monorepo structure of this project. These changes should be rejected, and the vulnerabilities should be addressed manually by updating the appropriate dependencies and regenerating the yarn.lock file.

[gemini-code-assist]

These changes are incorrect and will likely break the build. Replacing workspace:^ with pinned versions from the public registry defeats the purpose of a monorepo using Yarn workspaces. It forces this package to use different (and in this case, much older) versions of @backstage packages than the rest of the monorepo.

For example:

• @backstage/catalog-model is being downgraded from version 1.4.1 in the workspace to 0.1.1.
• @backstage/plugin-catalog-common is being downgraded from 1.0.15 to 0.1.0.
• @backstage/plugin-catalog-node is being downgraded from 1.4.1-next.0 to 1.0.0.

This will lead to version mismatches and likely cause compilation or runtime errors. The correct approach is to identify the root dependency causing the vulnerability and update it across the monorepo, then run yarn to update the lockfile. This PR should be closed and the fix should be applied manually.

    "@backstage/backend-tasks": "workspace:^",
    "@backstage/catalog-model": "workspace:^",
    "@backstage/config": "workspace:^",
    "@backstage/errors": "workspace:^",
    "@backstage/plugin-catalog-common": "workspace:^",
    "@backstage/plugin-catalog-node": "workspace:^"