Skip to content

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Jul 7, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/tech-insights-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 Cross-site Scripting (XSS)
SNYK-JS-ROLLUP-8073097
  576  

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:

🦉 Cross-site Scripting (XSS)

Summary by Sourcery

Bug Fixes:

  • Bump @backstage/catalog-model from workspace:^ to v0.1.1 to fix the SNYK-JS-ROLLUP-8073097 XSS issue

EntelligenceAI PR Summary

This PR locks the @backstage/catalog-model dependency to a specific version in the tech-insights-backend plugin.

  • Updated dependency version from workspace:^ to 0.1.1 in plugins/tech-insights-backend/package.json
  • Ensures version stability and predictable dependency resolution
  • May indicate preparation for package publishing or compatibility requirements
  • Affects build and distribution processes for the tech-insights-backend plugin

@codesandbox
Copy link

codesandbox bot commented Jul 7, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link

sourcery-ai bot commented Jul 7, 2025

Reviewer's Guide

Replaces local workspace reference of @backstage/catalog-model with an explicit 0.1.1 version to remediate a medium-severity XSS vulnerability and prompt a manual lockfile update.

File-Level Changes

Change Details Files
Bump @backstage/catalog-model to version 0.1.1 to fix vulnerability
  • Changed dependency spec from workspace:^ to 0.1.1 in package.json
  • Replaced local-use version with official release to drive lockfile regeneration
plugins/tech-insights-backend/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@snyk-io
Copy link
Author

snyk-io bot commented Jul 7, 2025

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

socket-security bot commented Jul 7, 2025

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

"@backstage/backend-tasks": "workspace:^",
"@backstage/catalog-client": "workspace:^",
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-model": "0.1.1",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replacing a workspace reference with a fixed version (0.1.1) breaks the monorepo's dependency management pattern. This change could lead to version conflicts with other packages that expect to use the same workspace-managed version of @backstage/catalog-model.

Additionally, the PR description indicates that the yarn.lock file failed to update, which must be resolved before merging.

Consider either:

  1. Updating all instances of this package throughout the monorepo to the same version
  2. Maintaining the workspace reference and updating the package version in the root package.json instead

This approach would preserve compatibility while addressing the security vulnerability.

Suggested change
"@backstage/catalog-model": "0.1.1",
"@backstage/catalog-model": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@github-actions
Copy link

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 Jul 14, 2025
@github-actions github-actions bot closed this Jul 19, 2025
@snyk-io snyk-io bot reopened this Jan 23, 2026
@entelligence-ai-pr-reviews
Copy link

Walkthrough

This pull request updates the dependency management for the tech-insights-backend plugin by changing the @backstage/catalog-model dependency from a workspace protocol reference to a pinned version. The change moves from using workspace:^ (which references the local workspace version) to a specific locked version 0.1.1. This modification ensures version stability and predictable dependency resolution, which is particularly important for package distribution and compatibility management. The change affects how the plugin resolves its dependencies during build and runtime, potentially improving consistency across different environments.

Changes

File(s) Summary
plugins/tech-insights-backend/package.json Changed @backstage/catalog-model dependency from workspace protocol reference (workspace:^) to pinned version 0.1.1 for version stability and compatibility.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Package as tech-insights-backend
    participant CatalogModel as @backstage/catalog-model
    participant Registry as Package Registry

    Note over Dev,Registry: Dependency Version Change

    Dev->>Package: Update package.json
    Note over Package: Change catalog-model<br/>from workspace:^ to 0.1.1
    
    Dev->>Package: Run package install
    Package->>Registry: Request @backstage/catalog-model@0.1.1
    Registry-->>Package: Return specific version 0.1.1
    Package->>CatalogModel: Install pinned version
    
    Note over Package,CatalogModel: Now using fixed version 0.1.1<br/>instead of workspace reference
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 github-actions bot removed the stale label Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant