[Snyk] Fix for 6 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• plugins/airbrake-backend/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 Handling of Unicode Encoding SNYK-JS-TAR-15038581	210
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	146
	UNIX Symbolic Link (Symlink) Following SNYK-JS-BACKSTAGEBACKENDPLUGINAPI-15054291	113
	Prototype Pollution SNYK-JS-LODASH-15053838	88
	Prototype Pollution SNYK-JS-LODASHES-15053836	88
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	62

---

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)
🦉 Prototype Pollution

---

EntelligenceAI PR Summary

This PR transitions the airbrake-backend plugin from workspace dependencies to explicit version pinning for three Backstage packages.

• Changed @backstage/backend-common from workspace:^ to 0.25.0
• Changed @backstage/backend-plugin-api from workspace:^ to 1.6.1
• Changed @backstage/config from workspace:^ to 0.1.1
• Enables independent package publishing or ensures consistent dependency versions across environments

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

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

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 security of the project by upgrading several vulnerable yarn dependencies within the airbrake-backend plugin. The changes mitigate known security risks by updating specific package versions, though a manual step is required to update the yarn.lock file to complete the fix.

Highlights

• Vulnerability Fixes: This pull request addresses 6 identified security vulnerabilities within the project's yarn dependencies, ranging from medium to high severity.
• Dependency Updates: Key dependencies in plugins/airbrake-backend/package.json have been updated to newer versions to resolve the identified vulnerabilities. Specifically, @backstage/backend-common was updated to 0.25.0, @backstage/backend-plugin-api to 1.6.1, and @backstage/config to 0.1.1.
• Manual yarn.lock Update Required: The automated process failed to update the yarn.lock file, which will require manual intervention to ensure consistency and proper dependency resolution, especially for zero-installs users.

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix 6 security vulnerabilities by updating dependencies in plugins/airbrake-backend/package.json. While the intent is good, the proposed changes are problematic. They switch from using local workspace packages (workspace:^) to pinned versions from the registry. This breaks the monorepo's dependency management. More critically, it downgrades @backstage/config to a very old version (0.1.1 from 1.0.8), which is highly likely to break the application. I have left a critical review comment with a suggestion to revert these changes and outlined a safer approach to resolving the vulnerabilities within the monorepo structure.

[gemini-code-assist]

This automated change from Snyk introduces several critical issues:

1. Breaks Monorepo Structure: Changing dependencies from workspace:^ to pinned versions decouples this package from the rest of the monorepo. This means it will no longer receive updates when the corresponding workspace packages are updated, leading to maintenance issues and potential inconsistencies.

2. Major Version Downgrade: The dependency @backstage/config is being pinned to version 0.1.1. However, the version in your workspace (packages/config/package.json) is 1.0.8. This is a significant downgrade that will almost certainly break the airbrake-backend plugin, as it's likely built against a much newer API.

3. Major Version Upgrades: The other dependencies, @backstage/backend-common and @backstage/backend-plugin-api, are being upgraded to versions (0.25.0 and 1.6.1 respectively) that are much newer than what's in your workspace (0.19.2-next.0 and 0.5.5-next.0). This could also introduce breaking API changes.

It is highly recommended to reject this change. The correct way to fix these vulnerabilities in a monorepo is to update the versions of the packages at the root of the workspace (e.g., in packages/backend-common/package.json). After updating the package versions there, run yarn install to update the yarn.lock file, which should resolve the transitive dependency vulnerabilities.

Given the high risk of breakage, I suggest reverting these changes.

    "@backstage/backend-common": "workspace:^",
    "@backstage/backend-plugin-api": "workspace:^",
    "@backstage/config": "workspace:^"

[entelligence-ai-pr-reviews]

Walkthrough

This PR updates the dependency management strategy for the airbrake-backend plugin by transitioning from workspace protocol references to explicit version pinning. Three Backstage packages are affected: @backstage/backend-common is pinned to version 0.25.0, @backstage/backend-plugin-api to version 1.6.1, and @backstage/config to version 0.1.1. This change moves away from the monorepo workspace dependency resolution pattern (workspace:^) to fixed version specifications, which is typically done when preparing a package for independent publication or to ensure consistent dependency versions across different deployment environments.

Changes

File(s)	Summary
plugins/airbrake-backend/package.json	Updated three Backstage dependencies from workspace protocol references (workspace:^) to pinned versions: @backstage/backend-common to 0.25.0, @backstage/backend-plugin-api to 1.6.1, and @backstage/config to 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Registry as NPM Registry
    
    Note over Dev,Registry: Dependency Version Update (No Code Changes)
    
    Dev->>PM: Update package.json<br/>Pin dependency versions
    Note over PM: @backstage/backend-common: workspace:^ → 0.25.0<br/>@backstage/backend-plugin-api: workspace:^ → 1.6.1<br/>@backstage/config: workspace:^ → 0.1.1
    
    Dev->>PM: npm install / yarn install
    PM->>Registry: Fetch pinned versions
    Registry-->>PM: Return packages
    PM-->>Dev: Dependencies updated
    
    Note over Dev: No runtime behavior changes<br/>Same functionality, locked versions

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.