Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Feb 2, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/ilert/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 Directory Traversal
SNYK-JS-TAR-15127355
  127  
medium severity 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 pins the @backstage/theme dependency to version 0.1.1 in the iLert plugin, replacing the workspace reference for improved version stability.

  • Modified @backstage/theme dependency from workspace:^ to 0.1.1 in plugins/ilert/package.json
  • Locks the theme package to a specific version instead of using local workspace version
  • Affects dependency resolution and ensures consistent theming functionality
  • May improve compatibility and API stability for the plugin

@codesandbox
Copy link

codesandbox bot commented Feb 2, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! 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 project's security posture by resolving two identified vulnerabilities: Directory Traversal and Uncontrolled Recursion. The fix involves a targeted upgrade of the @backstage/theme dependency within the plugins/ilert package. Reviewers should pay attention to the manual steps required for yarn.lock and zero-installs users.

Highlights

  • Security Vulnerability Fixes: This pull request addresses two security vulnerabilities: a 'Directory Traversal' (SNYK-JS-TAR-15127355) with a score of 127 and an 'Uncontrolled Recursion' (SNYK-JS-ESLINT-15102420) with a score of 45.
  • Dependency Upgrade: The @backstage/theme dependency in plugins/ilert/package.json has been upgraded from workspace:^ to version 0.1.1 to mitigate the identified vulnerabilities.
  • Yarn Lock File Warning: Snyk reported a failure to update the yarn.lock file, which will require manual intervention before merging. Users of Yarn's zero-installs feature will also need to run yarn to update their .yarn/cache/ directory.
Changelog
  • plugins/ilert/package.json
    • Updated the @backstage/theme dependency from workspace:^ to 0.1.1.
Activity
  • The pull request was automatically created by Snyk to address security vulnerabilities.
  • Snyk identified two vulnerabilities: Directory Traversal (medium severity) and Uncontrolled Recursion (medium severity).
  • The proposed fix involves upgrading the @backstage/theme dependency.
  • A warning was issued indicating that the yarn.lock file failed to update and requires manual resolution.
  • Guidance was provided for users leveraging Yarn's zero-installs feature, advising them to run yarn to update their cache.
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.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedreact@​17.0.21001007897100
Addedstorybook-dark-mode@​1.1.29910010080100
Addedswc-loader@​0.2.31001009285100
Addedreact-hot-loader@​4.13.19710010085100
Addedtypescript@​4.7.410010010010080
Addedreact-dom@​17.0.21001009098100

View full report

@socket-security
Copy link

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 polished under OFL-1.1

License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/docs/assets/fonts/LICENSE.txt)

From: ?npm/@storybook/addon-actions@6.5.16npm/polished@4.2.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/polished@4.2.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.

Warn High
License policy violation: npm typescript under W3C-20150513

License: W3C-20150513 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

License: MIT-Khronos-old - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt)

From: storybook/package.jsonnpm/typescript@4.7.4

ℹ 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/typescript@4.7.4. 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

snyk-io bot commented Feb 2, 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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, automatically generated by Snyk, aims to fix security vulnerabilities by upgrading the @backstage/theme package. However, the proposed change of pinning the version to 0.1.1 in plugins/ilert/package.json is incorrect for this monorepo setup. It replaces the workspace-local dependency with an old, published version, which is a downgrade and will likely lead to build or runtime issues. My review includes a critical comment to revert this change and maintain the workspace dependency.

"@backstage/errors": "workspace:^",
"@backstage/plugin-catalog-react": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",

Choose a reason for hiding this comment

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

critical

This change incorrectly replaces a workspace dependency with a pinned, older version. In a monorepo setup like this one, packages should use "workspace:^" to refer to other packages within the same repository. This ensures version consistency and that all plugins use the most up-to-date code from the workspace.

Pinning @backstage/theme to 0.1.1 is a significant downgrade from the current workspace version (0.4.1) and will likely cause dependency conflicts, duplicate modules, and runtime errors. This breaks the project's intended dependency management strategy.

The correct approach to fix vulnerabilities would be to address them within the @backstage/theme package itself, not by pinning a dependency in a consuming package. This automated change should be rejected.

Suggested change
"@backstage/theme": "0.1.1",
"@backstage/theme": "workspace:^",

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management for the iLert plugin by changing the @backstage/theme package from a workspace reference to a pinned version. The modification replaces the flexible workspace protocol (workspace:^) with a fixed version (0.1.1), establishing a hard dependency on a specific theme package version. This change impacts dependency resolution behavior and ensures the plugin uses a consistent, stable version of the theme API rather than relying on the local workspace version. The update may be driven by compatibility requirements or the need for predictable theming behavior across different environments.

Changes

File(s) Summary
plugins/ilert/package.json Changed @backstage/theme dependency from workspace reference (workspace:^) to pinned version (0.1.1).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant WS as Workspace
    participant NPM as NPM Registry
    
    Note over Dev,NPM: Dependency Resolution Change
    
    Dev->>PM: Install dependencies for ilert plugin
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/theme from workspace
        WS-->>PM: Return local workspace version
    else After Change (0.1.1)
        PM->>NPM: Fetch @backstage/theme@0.1.1
        NPM-->>PM: Return version 0.1.1
    end
    
    PM-->>Dev: Dependencies installed
    
    Note over Dev,NPM: No runtime behavior changes
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.

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.

3 participants