Skip to content

[Snyk] Fix for 1 vulnerabilities#12198

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-dea1d8df605b7cd6528470d2e7fb9cdb
Closed

[Snyk] Fix for 1 vulnerabilities#12198
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-dea1d8df605b7cd6528470d2e7fb9cdb

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Feb 13, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • plugins/techdocs/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
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  685  

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 techdocs plugin dependencies from workspace protocol to pinned package versions.

  • Updated @backstage/catalog-model from workspace:^ to version 0.1.1
  • Updated @backstage/plugin-search-react from workspace:^ to version 0.1.0
  • Changes made in plugins/techdocs/package.json
  • Indicates transition from local monorepo development to published package versions

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Feb 13, 2026

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
Copy link
Copy Markdown

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 High
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
Copy link
Copy Markdown

Walkthrough

This pull request updates the dependency management strategy for the techdocs plugin by replacing workspace protocol references with pinned package versions. The changes affect two Backstage dependencies: @backstage/catalog-model is pinned to version 0.1.1, and @backstage/plugin-search-react is pinned to version 0.1.0. This transition from workspace:^ to specific version numbers suggests a shift from local monorepo development to using published package versions, which is typically done during release preparation or to establish more explicit dependency version control.

Changes

File(s) Summary
plugins/techdocs/package.json Changed dependency resolution from workspace protocol (workspace:^) to pinned versions for @backstage/catalog-model (0.1.1) and @backstage/plugin-search-react (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Build as Build System
    participant TechDocs as TechDocs Plugin
    participant CatalogModel as @backstage/catalog-model
    participant SearchReact as @backstage/plugin-search-react
    
    Note over Build,SearchReact: Dependency Resolution Process
    
    Build->>TechDocs: Resolve dependencies
    
    alt Before Change (workspace:^)
        TechDocs->>Build: Request workspace version of catalog-model
        Build->>CatalogModel: Use local workspace version
        TechDocs->>Build: Request workspace version of search-react
        Build->>SearchReact: Use local workspace version
    else After Change (pinned versions)
        TechDocs->>Build: Request catalog-model@0.1.1
        Build->>CatalogModel: Use specific version 0.1.1
        TechDocs->>Build: Request search-react@0.1.0
        Build->>SearchReact: Use specific version 0.1.0
    end
    
    CatalogModel-->>TechDocs: Provide catalog model types/utilities
    SearchReact-->>TechDocs: Provide search UI components
    
    Note over TechDocs: TechDocs plugin now uses<br/>pinned dependency 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.

@github-actions
Copy link
Copy Markdown

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!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants