[Snyk] Security upgrade @backstage/core-plugin-api 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/code-coverage/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:

• Upgrade @backstage/core-plugin-api from local workspace reference to v0.1.0 in the code-coverage plugin to fix an 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-plugin-api dependency in the code-coverage plugin to version 0.1.0 to remediate a high-severity TarFS link-following vulnerability, and flags a manual yarn.lock update required due to automated lockfile failure.

Sequence Diagram: Snyk Automated Dependency Upgrade Process

sequenceDiagram
    title "Sequence Diagram: Snyk Automated Dependency Upgrade Process"
    actor SnykBot as "Snyk (Bot)"
    actor Developer
    participant ProjectRepository as "Project Repository"
    participant PackageFile as "plugins/code-coverage/package.json"
    participant YarnLock as "yarn.lock"

    SnykBot->>ProjectRepository: Scans dependencies
    SnykBot->>ProjectRepository: Detects vulnerability SNYK-JS-TARFS-10293725 in @backstage/core-plugin-api (v0.0.0-use.local)
    SnykBot->>ProjectRepository: Creates Pull Request to upgrade dependency
    activate SnykBot
    ProjectRepository->>PackageFile: Update "@backstage/core-plugin-api" from "0.0.0-use.local" to "0.1.0"
    SnykBot-->>YarnLock: Attempts to update yarn.lock (fails in this case)
    SnykBot-->>Developer: Warns: "Failed to update yarn.lock, please update manually before merging"
    deactivate SnykBot

Loading

File-Level Changes

Change	Details	Files
Bump core-plugin-api dependency to 0.1.0	Changed @backstage/core-plugin-api version from workspace:^ to 0.1.0 in package.json Noted automated lockfile update failed—yarn.lock must be regenerated manually	plugins/code-coverage/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 passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[graphite-app]

This change replaces the workspace reference with a fixed version number (0.1.0), which breaks the monorepo's workspace dependency structure. In a monorepo, workspace:^ ensures the package uses the local version from the workspace rather than downloading from npm.

Using a fixed version will:

1. Force fetching from npm instead of using local code
2. Create inconsistencies with other dependencies
3. Potentially break builds when local API changes aren't reflected

The dependency should remain as workspace:^ to maintain proper monorepo functionality while still addressing the security vulnerability through updates to the local package.

Suggested change

	"@backstage/core-plugin-api": "0.1.0",
	"@backstage/core-plugin-api": "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!