[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 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• plugins/cicd-statistics-module-gitlab/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
	Interpretation Conflict SNYK-JS-NODEFORGE-14114940	765
	Uncontrolled Recursion SNYK-JS-NODEFORGE-14125745	735

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

EntelligenceAI PR Summary

This PR pins the Backstage core plugin API dependency to a specific version in the GitLab CI/CD statistics plugin.

• Updated @backstage/core-plugin-api dependency from workspace:^ to 0.1.0 in package.json
• Transitions from local workspace version reference to explicit version declaration
• Likely preparation for publishing or resolving version compatibility issues
• Affects dependency resolution at build/install time

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

[entelligence-ai-pr-reviews]

Entelligence AI Vulnerability Scanner

Status: No security vulnerabilities found

Your code passed our comprehensive security analysis.

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the dependency management for the GitLab CI/CD statistics plugin by changing how it references the Backstage core plugin API. The modification replaces the workspace protocol reference with a fixed version number (0.1.0), effectively pinning the dependency to a specific version. This change transitions from using a local workspace version to an explicit version declaration, which typically indicates preparation for package publishing, improved dependency isolation, or resolution of version compatibility concerns. The change will affect how the plugin resolves and installs its core API dependency during the build process.

Changes

File(s)	Summary
plugins/cicd-statistics-module-gitlab/package.json	Changed @backstage/core-plugin-api dependency from workspace protocol reference (workspace:^) to fixed version 0.1.0, pinning the package to a specific version instead of using the local workspace version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant Package as cicd-statistics-module-gitlab
    participant CoreAPI as @backstage/core-plugin-api
    participant Registry as NPM Registry
    
    Note over Package,CoreAPI: Dependency Version Change
    
    Dev->>Package: Update package.json
    Note over Package: Change dependency from<br/>workspace:^ to 0.1.0
    
    alt Build with workspace reference (before)
        Package->>CoreAPI: Import from local workspace
        CoreAPI-->>Package: Use local development version
    else Build with fixed version (after)
        Package->>Registry: Request @backstage/core-plugin-api@0.1.0
        Registry-->>Package: Return published package v0.1.0
        Package->>CoreAPI: Import from npm package
        CoreAPI-->>Package: Use fixed version 0.1.0
    end
    
    Note over Package,CoreAPI: Plugin now uses pinned version<br/>instead of workspace reference

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]

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!