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/permission-react/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 transitions the permission-react plugin from workspace protocol dependencies to pinned version numbers for Backstage packages.

  • Updated @backstage/config dependency to explicit version 0.1.1
  • Updated @backstage/core-plugin-api dependency to explicit version 0.1.0
  • Updated @backstage/plugin-permission-common dependency to explicit version 0.1.0
  • Changes are declarative only in package.json with no functional code modifications
  • Likely preparation for independent package publication or stable release

@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 security posture of the project by upgrading several @backstage dependencies within the plugins/permission-react package. These updates are specifically targeted at resolving two identified vulnerabilities: a Directory Traversal issue and an Uncontrolled Recursion issue, thereby mitigating potential security risks.

Highlights

  • Dependency Updates: The @backstage/config dependency has been updated from workspace:^ to 0.1.1.
  • Dependency Updates: The @backstage/core-plugin-api dependency has been updated from workspace:^ to 0.1.0.
  • Dependency Updates: The @backstage/plugin-permission-common dependency has been updated from workspace:^ to 0.1.0.
  • Vulnerability Fixes: This PR addresses a 'Directory Traversal' vulnerability (SNYK-JS-TAR-15127355) with a score of 127.
  • Vulnerability Fixes: This PR addresses an 'Uncontrolled Recursion' vulnerability (SNYK-JS-ESLINT-15102420) with a score of 45.
Changelog
  • plugins/permission-react/package.json
    • Updated @backstage/config from workspace:^ to 0.1.1.
    • Updated @backstage/core-plugin-api from workspace:^ to 0.1.0.
    • Updated @backstage/plugin-permission-common from workspace:^ to 0.1.0.
Activity
  • This pull request was automatically created by Snyk to fix identified vulnerabilities.
  • The PR description includes a warning that the yarn.lock file failed to update and requires manual intervention.
  • Snyk has provided links to learn more about the vulnerabilities and customize PR templates.
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

@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 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: ?npm/@microsoft/api-extractor@7.33.7npm/typescript@4.8.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.8.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

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, attempts to fix two vulnerabilities by modifying dependencies in plugins/permission-react/package.json. However, the proposed changes are incorrect and will likely break the application. The PR downgrades several core @backstage packages to very old versions and removes the workspace:^ protocol, which is essential for this monorepo setup. These changes are highly likely to introduce breaking changes and build failures. Additionally, as noted in the PR description, the yarn.lock file has not been updated, which is another critical issue. I have left a comment with a suggestion to revert the changes and use yarn's resolutions feature to fix the transitive dependency vulnerabilities instead, which is a safer approach.

Comment on lines +34 to +36
"@backstage/config": "0.1.1",
"@backstage/core-plugin-api": "0.1.0",
"@backstage/plugin-permission-common": "0.1.0",

Choose a reason for hiding this comment

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

critical

These changes introduce significant downgrades to several @backstage dependencies and remove the workspace:^ protocol. This will likely break the package as it decouples it from the monorepo's versioning scheme. The versions are being downgraded from what's in the workspace (e.g., @backstage/config@1.0.8, @backstage/core-plugin-api@1.5.3) to very old versions (0.1.1, 0.1.0). This is a destructive change that will almost certainly cause build failures and runtime errors due to API incompatibilities.

Instead of these changes, consider reverting to workspace:^ and addressing the transitive dependency vulnerabilities (in tar and eslint) by adding a resolutions field to the root package.json to force newer, non-vulnerable versions of those packages.

    "@backstage/config": "workspace:^",
    "@backstage/core-plugin-api": "workspace:^",
    "@backstage/plugin-permission-common": "workspace:^"

@entelligence-ai-pr-reviews
Copy link

Walkthrough

This PR updates the dependency management strategy for the permission-react plugin package. The changes replace workspace protocol references (typically used in monorepo development) with explicit, pinned version numbers for three Backstage dependencies. Specifically, @backstage/config is pinned to version 0.1.1, while @backstage/core-plugin-api and @backstage/plugin-permission-common are both pinned to version 0.1.0. This modification is purely declarative, affecting only the package.json dependency specifications without any functional code changes. The update likely prepares the package for independent publication or establishes a stable release baseline with explicit version constraints.

Changes

File(s) Summary
plugins/permission-react/package.json Replaced workspace protocol references with explicit version numbers for three Backstage dependencies: @backstage/config (0.1.1), @backstage/core-plugin-api (0.1.0), and @backstage/plugin-permission-common (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PR as "permission-react Plugin"
    participant Config as "@backstage/config"
    participant CoreAPI as "@backstage/core-plugin-api"
    participant PermCommon as "@backstage/plugin-permission-common"
    
    Note over PR: Dependency Version Update
    Note over PR,PermCommon: Changed from workspace:^ to fixed versions
    
    PR->>Config: Depends on v0.1.1 (was workspace:^)
    PR->>CoreAPI: Depends on v0.1.0 (was workspace:^)
    PR->>PermCommon: Depends on v0.1.0 (was workspace:^)
    
    Note over PR,PermCommon: No functional code changes<br/>Package configuration only
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.

@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.

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.

3 participants