Skip to content

Add js-yaml merge key fix references#8363

Open
cookesan wants to merge 1 commit into
github:cookesan/advisory-improvement-8363from
cookesan:js-yaml-h67p-fix-references
Open

Add js-yaml merge key fix references#8363
cookesan wants to merge 1 commit into
github:cookesan/advisory-improvement-8363from
cookesan:js-yaml-h67p-fix-references

Conversation

@cookesan

@cookesan cookesan commented Jun 30, 2026

Copy link
Copy Markdown

Adds js-yaml merge key fix references to GHSA-h67p-54hq-rp68.

Audit refresh, July 8, 2026:

  • Confirmed the live PR is open, ready for review, merge-clean, and the visible advisory check is green.
  • Rechecked the merge-base diff: exactly one advisory JSON file changes (advisories/github-reviewed/2026/06/GHSA-h67p-54hq-rp68/GHSA-h67p-54hq-rp68.json), JSON parses, git diff --check passes, and the exact-head worktree is clean.
  • Revalidated the added public references and package-version evidence in the diff; all resolve through their source site or registry.

@github-actions github-actions Bot changed the base branch from main to cookesan/advisory-improvement-8363 June 30, 2026 01:00
@cookesan

cookesan commented Jul 7, 2026

Copy link
Copy Markdown
Author

Maintainer audit: this only expands the reference set for the js-yaml merge key advisory. The three upstream commits resolve, npm records for js-yaml 4.2.0 and 3.15.0 resolve, and CVE-2026-53550 is present in NVD. The advisory JSON parses, the committed diff passes git diff --check, the PR is merge-clean, and advisory processing is successful. No package, affected ranges, severity, or database metadata is changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant