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

[snyk-io]

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

Snyk changed the following file(s):

• plugins/jenkins-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
	Improper Link Resolution Before File Access ('Link Following') SNYK-JS-TARFS-10293725	721

---

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:

🦉 Improper Link Resolution Before File Access ('Link Following')

Summary by Sourcery

Bug Fixes:

• Upgrade @backstage/plugin-permission-common to 0.1.0 to fix a high-severity improper link resolution vulnerability

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's Guide

This PR replaces the local workspace reference for @backstage/plugin-permission-common with a fixed 0.1.0 version in package.json to remediate a high-severity vulnerability, and it requires a manual update of the yarn.lock file.

Sequence Diagram: Snyk PR Processing and Manual yarn.lock Update

sequenceDiagram
    actor Snyk
    participant "GitHub Repository" as Repo
    actor Developer

    Snyk->>Repo: Create PR (Upgrade @backstage/plugin-permission-common in plugins/jenkins-common/package.json)
    activate Repo
    Repo-->>Developer: Notify: PR created
    Repo-->>Developer: Warning: yarn.lock requires manual update
    deactivate Repo

    Developer->>Developer: 1. Review PR
    Developer->>Developer: 2. Update yarn.lock (e.g., run 'yarn')
    Developer->>Repo: Push updated yarn.lock
    Developer->>Repo: Merge PR

Loading

Class Diagram: Dependency Update in plugins/jenkins-common/package.json

classDiagram
  class `plugins_jenkins_common_package_json_dependencies` {
    <<Dependencies Section in plugins/jenkins-common/package.json>>
    -String "@backstage/plugin-permission-common": "workspace:^"
    +String "@backstage/plugin-permission-common": "0.1.0"
  }

Loading

File-Level Changes

Change	Details	Files
Dependency version bumped to fix vulnerability	Replaced workspace reference for @backstage/plugin-permission-common with explicit version 0.1.0 Noted that yarn.lock must be updated manually before merge	plugins/jenkins-common/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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[graphite-app]

This change replaces the workspace dependency pattern (workspace:^) with a fixed version (0.1.0), which breaks consistency with the monorepo's dependency management approach. Other Backstage packages in this repository use workspace references to maintain internal dependency alignment.

Using a fixed version instead of a workspace reference can lead to:

1. Version conflicts during dependency resolution
2. Difficulties when updating internal packages
3. Inconsistent behavior across the monorepo

The dependency should remain as workspace:^ to preserve the intended workspace dependency pattern used throughout the project.

Suggested change

	"@backstage/plugin-permission-common": "0.1.0"
	"@backstage/plugin-permission-common": "workspace:^"

Spotted by Diamond

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

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​uuid@​8.3.4
	@​types/​humanize-duration@​3.27.4
	react@​17.0.2
	@​types/​react@​19.1.6
	@​types/​git-url-parse@​9.0.3
	humanize-duration@​3.32.2
	dompurify@​2.5.8
	e2e-test@​0.0.0-use.local

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 for details)
Warn		tree-sitter@=0.22.1 has a License Policy Violation. License: Unicode-3.0 (package/vendor/tree-sitter/lib/src/unicode/LICENSE) From: ? → npm/tree-sitter@=0.22.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/tree-sitter@=0.22.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.

View full report

[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!