VULN-109557: fix: remediate vulnerable dependencies in splunk-example-ta - #46
Merged
Merged
Conversation
Remediates VULN-109557, VULN-109570, VULN-109578, VULN-109584, VULN-109586, and VULN-109587 by regenerating the npm lockfile with safe Storybook, tmp, uuid, and ws versions.
wtobis-splunk
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Regenerates the UI npm lockfile so the remaining vulnerable transitive dependencies resolve to safe versions. The lockfile continues to use public
registry.npmjs.orgpackage URLs.Remediated by this PR
storybooktmpuuidwswswsFiles changed
ui/package-lock.jsonValidation
npm ci --registry=https://registry.npmjs.orgnpm run lintnpm test -- --runInBand— 3 suites and 4 tests passednpm run build— completed successfully with size warnings only