[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/catalog-import/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
	Directory Traversal SNYK-JS-TAR-15032660	575

---

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)
🦉 Directory Traversal

---

EntelligenceAI PR Summary

This PR pins Backstage dependencies to specific versions in the catalog-import plugin, moving away from workspace references.

• Changed @backstage/core-components from workspace:^ to pinned version 0.8.6
• Changed @backstage/integration-react from workspace:^ to pinned version 0.1.1
• Transitions these packages from local workspace dependencies to external dependencies
• Modified in plugins/catalog-import/package.json

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the catalog-import plugin by replacing workspace references with pinned versions for two Backstage packages. The @backstage/core-components package is pinned to version 0.8.6, and @backstage/integration-react is pinned to version 0.1.1. This change transitions from using the monorepo workspace protocol (workspace:^) to explicit version numbers, indicating that these packages will now be consumed as external dependencies rather than local workspace packages. This modification is typically performed when preparing a package for independent publishing or resolving specific version compatibility requirements.

Changes

File(s)	Summary
plugins/catalog-import/package.json	Replaced workspace references with pinned versions for two dependencies: @backstage/core-components pinned to 0.8.6 and @backstage/integration-react pinned to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant CI as Build System
    participant PM as Package Manager
    participant CatalogImport as catalog-import Plugin
    participant CoreComponents as @backstage/core-components
    participant IntegrationReact as @backstage/integration-react

    Note over Dev,IntegrationReact: Dependency Version Pinning Change

    Dev->>CatalogImport: Update package.json
    Note right of Dev: Pin core-components to 0.8.6<br/>Pin integration-react to 0.1.1

    Dev->>CI: Commit & Push changes
    CI->>PM: Install dependencies
    
    PM->>CoreComponents: Fetch version 0.8.6 (pinned)
    CoreComponents-->>PM: Return specific version
    
    PM->>IntegrationReact: Fetch version 0.1.1 (pinned)
    IntegrationReact-->>PM: Return specific version
    
    PM-->>CI: Dependencies resolved
    CI->>CatalogImport: Build plugin with pinned versions
    CatalogImport-->>CI: Build successful
    
    Note over CatalogImport,IntegrationReact: Plugin now uses fixed versions<br/>instead 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.

[entelligence-ai-pr-reviews]

Correctness: Internal monorepo dependencies must use workspace:^ to ensure local linking. Pinning specific versions (0.8.6, 0.1.1) causes duplicate package installations and breaks runtime singletons. Revert these to workspace:^.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

File: plugins/catalog-import/package.json
Lines: 38-42

Problem: Two Backstage dependencies have been changed from workspace protocol (`workspace:^`) to pinned versions (`0.8.6` and `0.1.1`), breaking monorepo consistency.

Required Fix:
1. Revert `@backstage/core-components` from `"0.8.6"` to `"workspace:^"`
2. Revert `@backstage/integration-react` from `"0.1.1"` to `"workspace:^"`
3. If these pinned versions were intentional workarounds for breaking changes, add inline comments explaining why and create a tracking issue to restore workspace protocol
4. Run `yarn install` to regenerate lockfile with workspace references
5. Verify no type errors exist after restoration

Context: All other Backstage packages in this file use `workspace:^` — this is the standard monorepo pattern to ensure coordinated version updates across the workspace.

✨ Committable Code Suggestion

💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.

Suggested change

	"@backstage/core-components": "0.8.6",
	"@backstage/core-plugin-api": "workspace:^",
	"@backstage/errors": "workspace:^",
	"@backstage/integration": "workspace:^",
	"@backstage/integration-react": "workspace:^",
	"@backstage/integration-react": "0.1.1",
	"dependencies": {
	"@backstage/catalog-client": "workspace:^",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/config": "workspace:^",
	"@backstage/core-components": "workspace:^",
	"@backstage/core-plugin-api": "workspace:^",
	"@backstage/errors": "workspace:^",
	"@backstage/integration": "workspace:^",
	"@backstage/integration-react": "workspace:^",
	"@backstage/plugin-catalog-common": "workspace:^",
	"@backstage/plugin-catalog-react": "workspace:^",
	"@material-ui/core": "^4.12.2",

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