[Snyk] Security upgrade @backstage/plugin-permission-common from 0.0.0-use.local to 0.1.0

[q1blue]

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

Snyk changed the following file(s):

• plugins/playlist-common/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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	62

---

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)
🦉 Allocation of Resources Without Limits or Throttling

---

EntelligenceAI PR Summary

This PR pins the @backstage/plugin-permission-common dependency to a specific version in the playlist-common plugin.

• Changed dependency version from workspace:^ to 0.1.0 in plugins/playlist-common/package.json
• Replaces local workspace reference with published package version
• Establishes stable dependency boundary for package publication readiness

[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, focuses on enhancing the project's security posture by upgrading a critical dependency. It specifically targets and resolves identified vulnerabilities within the @backstage/plugin-permission-common package, ensuring a more secure application environment.

Highlights

• Security Upgrade: Upgraded the @backstage/plugin-permission-common dependency from workspace:^ to 0.1.0 to address two identified security vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) and a medium-severity Allocation of Resources Without Limits or Throttling.
• Manual Intervention Required: The yarn.lock file failed to update automatically and requires manual intervention before merging. Additionally, users leveraging Yarn's zero-installs feature will need to run yarn to update their .yarn/cache directory.

Changelog

• plugins/playlist-common/package.json
  • Updated the version of @backstage/plugin-permission-common to 0.1.0.

Activity

• Snyk automatically created this pull request to fix identified security vulnerabilities.
• Snyk reported a failure to update the yarn.lock file, indicating a manual update is required.

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​docusaurus/​module-type-aliases@​0.0.0-5591
	@​docusaurus/​preset-classic@​0.0.0-5591
	@​spotify/​prettier-config@​14.1.3
	@​docusaurus/​plugin-client-redirects@​0.0.0-5591
	@​docusaurus/​core@​0.0.0-5591
	@​types/​webpack-env@​1.18.1
	@​tsconfig/​docusaurus@​1.0.7
	@​types/​luxon@​3.3.0
	docusaurus-plugin-sass@​0.2.4
	react@​17.0.2
	clsx@​1.2.1
	js-yaml@​3.13.1 ⏵ 4.1.0	-1
	swc-loader@​0.2.3
	luxon@​2.5.2 ⏵ 3.3.0	+3		+1
	prism-react-renderer@​1.3.5
	yaml-loader@​0.8.0
	react-dom@​17.0.2
	@​swc/​core@​1.3.68
	sass@​1.60.0
	prettier@​2.8.8

View full report

[socket-security]

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		License policy violation: npm argparse under Python-2.0.1 License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE) From: ? → npm/js-yaml@4.1.0 → npm/argparse@2.0.1 ℹ 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/argparse@2.0.1. 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		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/@docusaurus/module-type-aliases@0.0.0-5591 → npm/caniuse-lite@1.0.30001481 ℹ 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/caniuse-lite@1.0.30001481. 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		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@docusaurus/core@0.0.0-5591 → npm/@docusaurus/plugin-client-redirects@0.0.0-5591 → npm/@docusaurus/preset-classic@0.0.0-5591 → npm/entities@4.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. 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

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the playlist-common plugin by replacing a workspace protocol reference with a fixed version number. The change modifies the @backstage/plugin-permission-common dependency from workspace:^ to version 0.1.0, effectively pinning it to a specific published version. This transition from a local workspace reference to a fixed version typically indicates that the package is being prepared for publication or that the team is establishing more stable dependency boundaries between packages in the monorepo. This ensures consistent behavior across different environments and installations.

Changes

File(s)	Summary
plugins/playlist-common/package.json	Updated @backstage/plugin-permission-common dependency from workspace protocol reference (workspace:^) to fixed version 0.1.0.

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
    participant PC as playlist-common

    Note over Dev,PC: Dependency Resolution Change

    Dev->>PC: Update package.json
    Note right of PC: Change dependency from<br/>workspace:^ to 0.1.0

    Dev->>PM: Install dependencies
    
    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/plugin-permission-common
        WS-->>PM: Return local workspace package
        PM->>PC: Link local dependency
    else After Change (0.1.0)
        PM->>NPM: Fetch @backstage/plugin-permission-common@0.1.0
        NPM-->>PM: Return published package
        PM->>PC: Install published dependency
    end

    Note over PC: playlist-common now uses<br/>published version 0.1.0

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 updates the @backstage/plugin-permission-common dependency in plugins/playlist-common/package.json from workspace:^ to 0.1.0. This change addresses two identified vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS) and a medium-severity Allocation of Resources Without Limits or Throttling issue. The update is a direct dependency version bump, which is a straightforward fix for the reported security concerns. It's important to ensure that this specific version 0.1.0 of @backstage/plugin-permission-common indeed contains the fixes for the mentioned vulnerabilities and that there are no breaking changes introduced by this specific version that are not handled in the current codebase. The PR description also notes a failure to update yarn.lock, which will require manual intervention before merging.

[github-actions]

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!