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

[snyk-io]

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

Snyk changed the following file(s):

• plugins/analytics-module-newrelic-browser/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
	Improper Link Resolution Before File Access ('Link Following') SNYK-JS-TARFS-10293725	721

---

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:

🦉 Improper Link Resolution Before File Access ('Link Following')

Summary by Sourcery

Bug Fixes:

• Bump @backstage/core-components from workspace:^ to 0.1.0 to fix a high-severity improper link resolution vulnerability.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[sourcery-ai]

Reviewer's Guide

This PR upgrades the @backstage/core-components dependency in the analytics-module-newrelic-browser plugin from a local workspace reference to version 0.1.0 to resolve a high-severity tarfs vulnerability; reviewers should confirm compatibility and update the lockfile manually before merging.

Sequence Diagram: Snyk Automated Vulnerability Fix Process

sequenceDiagram
    actor Snyk
    participant Repository
    participant PackageFile as "plugins/analytics-module-newrelic-browser/package.json"

    Snyk->>Repository: Scans for vulnerabilities
    activate Snyk
    Snyk->>PackageFile: Identifies '@backstage/core-components: "workspace:^"' (vulnerable: SNYK-JS-TARFS-10293725)
    Snyk->>Snyk: Determines upgrade to '@backstage/core-components: "0.1.0"'
    Snyk->>Repository: Creates Pull Request with change for PackageFile
    activate Repository
    Repository->>PackageFile: Updates '@backstage/core-components' to "0.1.0"
    deactivate Repository
    Snyk->>Repository: Posts PR description (details, yarn.lock warning)
    deactivate Snyk

Loading

File-Level Changes

Change	Details	Files
Bump @backstage/core-components dependency to 0.1.0	Changed version spec from workspace:^ to 0.1.0	plugins/analytics-module-newrelic-browser/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

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

Icon	Severity	Issues
	Critical	0
	High	0
	Medium	1
	Low	0

⛔ security/snyk check is complete. 1 issues have been found. (View Details)

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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

[graphite-app]

This change replaces the workspace dependency with a fixed version, which breaks the monorepo's dependency management pattern. In a Backstage monorepo, dependencies between internal packages should use workspace:^ to ensure consistent versioning across the codebase.

While addressing the security vulnerability is important, changing to a fixed version 0.1.0 will:

1. Pull the package from the npm registry instead of using the local version
2. Potentially cause version conflicts with other components
3. Make future updates more difficult to manage

Consider addressing the security vulnerability while maintaining the workspace reference pattern. This might involve updating the vulnerable dependency within your local @backstage/core-components package instead.

Suggested change

	"@backstage/core-components": "0.1.0",
	"@backstage/core-components": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

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