Skip to content

[Snyk] Fix for 4 vulnerabilities#10605

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-51b3c9a3749d7e63f2bf12485200a2da
Closed

[Snyk] Fix for 4 vulnerabilities#10605
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-51b3c9a3749d7e63f2bf12485200a2da

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jan 23, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/catalog-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
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DIFF-14917201
  590  
high severity UNIX Symbolic Link (Symlink) Following
SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291
  550  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  545  
medium severity Prototype Pollution
SNYK-JS-LODASHES-15053836
  545  

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)
🦉 Prototype Pollution


EntelligenceAI PR Summary

Updates dependency management in catalog-backend plugin from workspace references to fixed versions and upgrades lodash for security.

  • Converted 11 Backstage packages from workspace:^ to explicit versions
  • Pinned @backstage/backend-common to 0.24.1
  • Pinned @backstage/backend-plugin-api to 1.6.1
  • Updated catalog-related packages (@backstage/catalog-client, @backstage/catalog-model, @backstage/plugin-catalog-common, @backstage/plugin-catalog-node)
  • Updated plugin packages (@backstage/plugin-permission-common, @backstage/plugin-permission-node, @backstage/plugin-search-common)
  • Upgraded lodash from ^4.17.21 to ^4.17.23

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 23, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@socket-security
Copy link
Copy Markdown

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 High
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

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jan 23, 2026

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
Copy link
Copy Markdown

Walkthrough

This PR updates the dependency management strategy for the catalog-backend plugin by transitioning from workspace protocol references to explicit version numbers for eleven internal Backstage packages. The changes include pinning versions for core packages such as backend-common (0.24.1), backend-plugin-api (1.6.1), and various catalog and plugin packages. Additionally, the lodash dependency is upgraded from ^4.17.21 to ^4.17.23, likely addressing known security vulnerabilities. This modification indicates a shift from monorepo workspace dependency resolution to fixed versioning, potentially in preparation for package publication or to enforce stricter version control across the project.

Changes

File(s) Summary
plugins/catalog-backend/package.json Converted eleven Backstage dependencies from workspace protocol (workspace:^) to explicit version numbers and upgraded lodash from ^4.17.21 to ^4.17.23.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Deps as Dependencies
    
    Note over Dev,Deps: Dependency Version Updates
    
    Dev->>PM: Update package.json versions
    Note right of PM: Changes:<br/>- backend-common: workspace → 0.24.1<br/>- backend-plugin-api: workspace → 1.6.1<br/>- integration: workspace → 0.1.0<br/>- plugin-auth-node: workspace → 0.1.0<br/>- plugin-events-node: workspace → 0.4.0<br/>- plugin-scaffolder-common: workspace → 0.1.0<br/>- search-backend-module-catalog: workspace → 0.2.0<br/>- search-common: workspace → 0.3.1<br/>- lodash: 4.17.21 → 4.17.23
    
    Dev->>PM: Run install command
    PM->>Deps: Resolve and fetch updated versions
    Deps-->>PM: Return packages
    PM-->>Dev: Dependencies updated
    
    Note over Dev,Deps: No code logic changes<br/>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
Copy link
Copy Markdown

github-actions Bot commented Apr 2, 2026

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!

@github-actions github-actions Bot added the stale label Apr 2, 2026
@github-actions github-actions Bot closed this Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants