[Snyk] Fix for 3 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• packages/core-plugin-api/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
	Interpretation Conflict SNYK-JS-NODEFORGE-14114940	178
	Uncontrolled Recursion SNYK-JS-NODEFORGE-14125745	125
	Integer Overflow or Wraparound SNYK-JS-NODEFORGE-14125097	44

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

EntelligenceAI PR Summary

This PR transitions internal package dependencies from workspace protocol to fixed versions in the core-plugin-api package.

• Changed @backstage/config dependency from workspace:^ to fixed version 0.1.1
• Changed @backstage/version-bridge dependency from workspace:^ to fixed version 0.1.0
• Modified packages/core-plugin-api/package.json to use explicit version numbers instead of workspace protocol
• Likely part of release preparation or dependency management strategy update

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

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react@​17.0.2
	storybook-dark-mode@​1.1.2
	swc-loader@​0.2.3
	react-hot-loader@​4.13.1
	typescript@​4.7.4
	react-dom@​17.0.2

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 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: storybook/package.json → npm/@storybook/addon-actions@6.5.16 → npm/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		License policy violation: npm typescript under MIT-Khronos-old License: MIT-Khronos-old - 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) From: storybook/package.json → npm/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

[entelligence-ai-pr-reviews]

Entelligence AI Vulnerability Scanner

Status: No security vulnerabilities found

Your code passed our comprehensive security analysis.

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the @backstage/core-plugin-api package by transitioning from workspace protocol references to fixed version specifications. Two internal dependencies are affected: @backstage/config is pinned to version 0.1.1 and @backstage/version-bridge is pinned to version 0.1.0. This change replaces the flexible workspace:^ protocol with explicit version numbers, which typically indicates preparation for package publication or a shift in how dependencies are resolved within the monorepo structure. This ensures consistent dependency versions across environments and may be part of a broader release management or versioning strategy.

Changes

File(s)	Summary
packages/core-plugin-api/package.json	Updated dependency specifications from workspace protocol (workspace:^) to fixed versions: @backstage/config to 0.1.1 and @backstage/version-bridge to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as core-plugin-api Package
    participant Config as @backstage/config
    participant Bridge as @backstage/version-bridge
    
    Note over Dev,Bridge: Dependency Version Pinning Change
    
    Dev->>PKG: Update package.json dependencies
    
    rect rgb(255, 240, 240)
        Note over PKG,Config: Before: workspace:^ (monorepo reference)
    end
    
    rect rgb(240, 255, 240)
        Note over PKG,Config: After: Fixed versions
    end
    
    PKG->>Config: Resolve dependency<br/>Version: 0.1.1 (pinned)
    activate Config
    Config-->>PKG: Provide config functionality
    deactivate Config
    
    PKG->>Bridge: Resolve dependency<br/>Version: 0.1.0 (pinned)
    activate Bridge
    Bridge-->>PKG: Provide version bridge functionality
    deactivate Bridge
    
    Note over PKG: Dependencies now use<br/>published versions instead<br/>of workspace references

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.