[Snyk] Security upgrade @backstage/theme from 0.0.0-use.local to 0.1.1

[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/splunk-on-call/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
	Directory Traversal SNYK-JS-TAR-15127355	510

---

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:

🦉 Directory Traversal

---

EntelligenceAI PR Summary

This PR pins the @backstage/theme dependency to version 0.1.1 in the Splunk On-Call plugin, replacing the workspace reference.

• Modified dependency declaration in plugins/splunk-on-call/package.json
• Changed from workspace:^ to explicit version 0.1.1
• Locks the theme package to a specific version for stability or compatibility purposes

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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

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

Walkthrough

This pull request modifies the dependency management for the Splunk On-Call plugin by changing how the Backstage theme package is referenced. Instead of using a workspace reference that points to the local monorepo version, the dependency is now pinned to a specific version (0.1.1). This change suggests a move towards more controlled dependency versioning, potentially to address compatibility issues or ensure consistent behavior across different environments. The modification affects only the package.json file and represents a shift from dynamic workspace-based dependency resolution to explicit version pinning.

Changes

File(s)	Summary
plugins/splunk-on-call/package.json	Changed @backstage/theme dependency from workspace reference (workspace:^) to pinned version 0.1.1.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Plugin as Splunk-on-Call Plugin
    participant Theme as @backstage/theme

    Dev->>PM: Update package.json dependency
    Note over PM: Change @backstage/theme<br/>from workspace:^ to 0.1.1
    
    Dev->>PM: npm/yarn install
    PM->>Theme: Resolve @backstage/theme@0.1.1
    Theme-->>PM: Return specific version 0.1.1
    PM->>Plugin: Install theme dependency
    Note over Plugin,Theme: Plugin now uses pinned<br/>version instead of workspace

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.

[entelligence-ai-pr-reviews]

Correctness: The change to @backstage/theme from workspace:^ to 0.1.1 breaks monorepo dependency resolution. This will cause version mismatches with other workspace packages, leading to runtime errors. Revert to workspace:^.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

File: plugins/splunk-on-call/package.json
Line: 40

Problem: The dependency `@backstage/theme` has been changed from `workspace:^` to a pinned version `0.1.1`, breaking the monorepo workspace protocol used by all other Backstage dependencies in this package.

Fix Instructions:
1. Revert the change to use `workspace:^` instead of `0.1.1`
2. Ensure consistency with other Backstage dependencies: `@backstage/catalog-model`, `@backstage/core-components`, `@backstage/core-plugin-api`, and `@backstage/plugin-catalog-react` all use `workspace:^`
3. If a specific version is required, document the reason and verify compatibility with the workspace build system
4. Test that the package builds correctly within the monorepo context after the change

✨ Committable Code Suggestion

💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.

Suggested change

	"@backstage/theme": "0.1.1",
	"@backstage/catalog-model": "workspace:^",
	"@backstage/core-components": "workspace:^",
	"@backstage/core-plugin-api": "workspace:^",
	"@backstage/plugin-catalog-react": "workspace:^",
	"@backstage/theme": "workspace:^",
	"@material-ui/core": "^4.12.2",
	"@material-ui/icons": "^4.9.1",
	"@material-ui/lab": "4.0.0-alpha.61",