[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 2 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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	590
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	550

---

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)

---

EntelligenceAI PR Summary

This PR pins the @backstage/plugin-permission-common dependency to version 0.1.0 in the jenkins-common plugin package.

• Replaced workspace protocol reference (workspace:^) with fixed version specifier (0.1.0)
• Change affects dependency resolution during package installation
• May indicate preparation for package publishing or resolution of version compatibility issues
• Impacts monorepo workspace dependency resolution behavior

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

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 atob under CC-BY-3.0 License: CC-BY-3.0 - the applicable license policy does not allow this license (4) (package/LICENSE.DOCS) From: ? → npm/atob@2.1.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/atob@2.1.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.

View full report

[entelligence-ai-pr-reviews]

Walkthrough

This pull request modifies the dependency management for the jenkins-common plugin by changing how the @backstage/plugin-permission-common dependency is resolved. The change replaces the workspace protocol reference with a fixed version number (0.1.0), effectively pinning the dependency to a specific release. This modification likely indicates preparation for package publication or addresses version compatibility requirements. The change will affect how the dependency is resolved during package installation and may have implications for monorepo workspace dependency resolution strategies.

Changes

File(s)	Summary
plugins/jenkins-common/package.json	Changed @backstage/plugin-permission-common dependency from workspace protocol (workspace:^) to fixed version 0.1.0, pinning the dependency to a specific release version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Local as Local Workspace
    participant NPM as NPM Registry
    
    Note over Dev,NPM: Dependency Resolution Change
    
    Dev->>PM: Install dependencies
    
    alt Before Change (workspace:^)
        PM->>Local: Resolve @backstage/plugin-permission-common
        Local-->>PM: Return local package
    else After Change (0.1.0)
        PM->>NPM: Fetch @backstage/plugin-permission-common@0.1.0
        NPM-->>PM: Return published package
    end
    
    PM-->>Dev: Dependencies installed
    
    Note over Dev,NPM: No runtime behavior changes<br/>Only affects dependency resolution

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.