fix(docs-site): resolve high-severity js-yaml npm audit finding#6450
Merged
Conversation
Bump transitive deps via 'npm audit fix' to clear the high-severity js-yaml advisory (GHSA-52cp-r559-cp3m) that was failing the dependency-audit workflow's --audit-level=high gate: - js-yaml 4.2.0 -> 4.3.0 (high: quadratic CPU via YAML merge keys) - dompurify -> 3.4.12 (moderate: ALLOWED_ATTR pollution) - astro 6.4.6 -> 6.4.8 (patch) Only the lockfile changes; package.json ranges already permit these. Remaining astro-related moderate advisories require a breaking major bump and are out of scope for this audit-gate fix.
Contributor
Contributor
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
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.
What
Clears the high-severity `js-yaml` advisory that is failing the `dependency-audit` workflow's `--audit-level=high` gate for the docs-site package.
Applied via `npm audit fix` (non-breaking, lockfile-only):
Only `docs-site/package-lock.json` changes — existing `package.json` version ranges already permit these.
Why
The `Audit Docs Site Package` job in `dependency-audit.yml` fails on any high/critical finding. This unblocks that gate (e.g. on #6445 and any other PR).
Verification
Out of scope