[Snyk] Security upgrade @backstage/core-plugin-api from 0.0.0-use.local to 0.1.0

[q1blue]

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

Snyk changed the following file(s):

• plugins/nomad/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
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235959	84
	Server-side Request Forgery (SSRF) SNYK-JS-WEBPACK-15235969	84

---

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:

🦉 Server-side Request Forgery (SSRF)

---

EntelligenceAI PR Summary

This PR pins the @backstage/core-plugin-api dependency to version 0.1.0 in the Nomad plugin, breaking the monorepo workspace pattern.

• Replaced workspace:^ with 0.1.0 for @backstage/core-plugin-api dependency
• Deviates from the workspace pattern used by other Backstage dependencies in the same file
• May affect dependency resolution and introduce potential version conflicts
• Could indicate preparation for external publication or specific compatibility requirements

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security by upgrading a key dependency. The primary objective is to mitigate identified Server-side Request Forgery (SSRF) vulnerabilities through the update of @backstage/core-plugin-api to a more secure version.

Highlights

• Dependency Upgrade: The @backstage/core-plugin-api dependency has been upgraded from workspace:^ (effectively 0.0.0-use.local) to 0.1.0 in plugins/nomad/package.json.
• Security Fix: This upgrade addresses two Server-side Request Forgery (SSRF) vulnerabilities (SNYK-JS-WEBPACK-15235959 and SNYK-JS-WEBPACK-15235969), each with a severity score of 84.
• Yarn Zero-Installs Note: Users leveraging Yarn's zero-installs feature will need to manually run yarn to update the .yarn/cache/ directory, as the yarn.lock file was not updated by this PR.

Changelog

• plugins/nomad/package.json
  • Updated the version of @backstage/core-plugin-api from workspace:^ to 0.1.0.

Activity

• This pull request was automatically created by Snyk to resolve security vulnerabilities.
• A warning is present indicating that the yarn.lock file failed to update and requires manual intervention.
• The PR description advises users of Yarn's zero-install feature to run yarn to update their local cache.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, attempts to fix security vulnerabilities by upgrading @backstage/core-plugin-api. However, the proposed change is incorrect as it replaces a Yarn workspace-protocol dependency ("workspace:^") with a hardcoded and significantly outdated version ("0.1.0"). This breaks the monorepo's dependency management and should not be merged. The change needs to be reverted, and the vulnerabilities should be addressed by performing a proper dependency upgrade that respects the monorepo structure.

[gemini-code-assist]

This change from "workspace:^" to a hardcoded version "0.1.0" is incorrect for this monorepo setup. The workspace: protocol is essential for linking packages within the same Yarn workspace, ensuring consistency and proper local development.

Pinning to a specific version, especially a very outdated one like 0.1.0 (the version in the workspace is 1.5.3), will break dependency resolution and likely cause build or runtime failures. This automated change should be reverted. The underlying security vulnerabilities should be addressed by updating dependencies correctly across the monorepo, which will also allow the yarn.lock file to be updated properly.

Suggested change

	"@backstage/core-plugin-api": "0.1.0",
	"@backstage/core-plugin-api": "workspace:^",

[entelligence-ai-pr-reviews]

Walkthrough

This PR modifies the dependency management for the Nomad plugin by changing the @backstage/core-plugin-api dependency from a workspace reference to a pinned version. The change replaces the monorepo workspace pattern (workspace:^) with a specific version (0.1.0), which deviates from the standard Backstage dependency management approach used by other dependencies in the same package. This modification could indicate preparation for external package publication, a specific compatibility requirement, or a temporary workaround. The change may impact dependency resolution behavior and could potentially introduce version conflicts if the workspace version differs from the pinned version.

Changes

File(s)	Summary
plugins/nomad/package.json	Changed @backstage/core-plugin-api dependency from workspace reference (workspace:^) to pinned version (0.1.0).

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant PM as Package Manager
    participant NP as Nomad Plugin
    participant WS as Workspace
    participant NPM as NPM Registry

    Note over PM,NPM: Dependency Resolution Process

    PM->>NP: Read package.json
    NP-->>PM: Dependencies list

    alt Before Change (workspace:^)
        PM->>WS: Resolve @backstage/core-plugin-api
        WS-->>PM: Return local workspace version
    else After Change (0.1.0)
        PM->>NPM: Fetch @backstage/core-plugin-api@0.1.0
        NPM-->>PM: Return specific version 0.1.0
    end

    PM->>NP: Install resolved dependency
    Note over NP: Nomad plugin now uses<br/>pinned version 0.1.0

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.

[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

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