[Snyk] Fix for 2 vulnerabilities

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

• Changed @backstage/config from workspace:^ to 0.1.1
• Changed @backstage/core-components from workspace:^ to 0.1.0
• Changed @backstage/core-plugin-api from workspace:^ to 0.1.0
• Indicates preparation for package publication or dependency stabilization

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​storybook/​testing-library@​0.2.0
	@​storybook/​node-logger@​6.5.16
	@​storybook/​addons@​6.5.16
	@​storybook/​builder-webpack5@​6.5.16
	@​storybook/​manager-webpack5@​6.5.16
	@​storybook/​addon-actions@​6.5.16
	@​storybook/​react@​6.5.16
	@​swc/​core@​1.3.68
	@​storybook/​addon-storysource@​6.5.16
	@​storybook/​addon-controls@​6.5.16
	@​storybook/​addon-a11y@​6.5.16
	@​storybook/​addon-links@​6.5.16

View full report

[snyk-io]

⛔ Snyk checks have failed. 1 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (1)
⛔	Open Source Security	0	0	1	0	1 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.
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/@storybook/addon-controls@6.5.16 → npm/@storybook/builder-webpack5@6.5.16 → npm/@storybook/manager-webpack5@6.5.16 → npm/@storybook/react@6.5.16 → npm/caniuse-lite@1.0.30001378 ℹ 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.30001378. 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 PR updates the dependency management strategy for the config-schema plugin by replacing workspace protocol references with explicit version numbers. Three Backstage packages are affected: @backstage/config is pinned to version 0.1.1, while @backstage/core-components and @backstage/core-plugin-api are both pinned to version 0.1.0. This transition from workspace:^ to fixed versions suggests the package is being prepared for external publication or moving away from monorepo workspace dependency resolution to ensure version stability and reproducibility across different environments.

Changes

File(s)	Summary
plugins/config-schema/package.json	Updated dependency version specifications from workspace protocol (workspace:^) to explicit versions: @backstage/config to 0.1.1, @backstage/core-components and @backstage/core-plugin-api to 0.1.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PKG as config-schema/package.json
    participant PM as Package Manager
    participant Deps as External Dependencies

    Note over Dev,Deps: Dependency Version Update Process

    Dev->>PKG: Update dependency versions
    Note right of PKG: @backstage/config: workspace:^ → 0.1.1<br/>@backstage/core-components: workspace:^ → 0.1.0<br/>@backstage/core-plugin-api: workspace:^ → 0.1.0

    Dev->>PM: Run install command
    PM->>PKG: Read package.json
    PM->>Deps: Resolve specific versions
    Deps-->>PM: Return version 0.1.1 (config)
    Deps-->>PM: Return version 0.1.0 (core-components)
    Deps-->>PM: Return version 0.1.0 (core-plugin-api)
    PM->>PM: Install pinned versions
    PM-->>Dev: Dependencies installed

    Note over Dev,Deps: Workspace references replaced with fixed versions

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.