Repository navigation
Conversation
d3xter666
marked this pull request as draft
October 8, 2026 06:28
Keep in mind that there will be CodeQL security advisories here. It's just for testing purposes
This branch has not been deployed
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.
Why audit three ways, not one
The workflow runs the audit from three angles, to separate what we tested from what users get from our full dev surface:
npm cipackage-lock.jsonpins — the reproducible tree we build & test against.npm install,--skip-dev@ui5/cliinstall gives users today. The one that matters most.npm installGoal: catch advisories that reach users (or our build) before Dependabot does, and know which bucket each finding sits in so we can prioritize. Each variant runs independently (
fail-fast: false), so one failing never hides the others.