chore(deps): bump agent-governance-sdk to 5.0.0 in the three CLI packages, with audit

[Imran Siddique (imran-siddique)]

Consolidates the SDK 4.0.0 to 5.0.0 updates from #3686, #3683 and #3681 across the three CLI packages, with the dependency audit required for a major update.

The installed js-yaml remains 4.2.0: all three package manifests override the published SDK's declared 5.2.1 pin. This PR clears none of the three listed 4.x advisories. #3843/#3844/#3875 raise the override to 4.3.1 and address the first two; #3894 raises it to 4.3.2 and addresses all three. Land that parser fix first, then reconcile this SDK bump while preserving the patched override. #3894 overlaps all six package manifest/lockfile paths here.

The original Dependabot updates are retained with their authorship and signoffs. Review corrections restored the root override metadata in all three lockfiles, so the current files are no longer byte-identical to the original Dependabot output. The audit now distinguishes declared and resolved dependencies, dates the September 3 audit, and records the third advisory published September 8. The earlier description's claim that this bump exchanged two HIGH advisories for one was incorrect.

Validation for the September 14 correction: checked the SDK pin, parser resolution, and matching root overrides in all three manifest/lockfile pairs; scoped documentation link and strict frontmatter checks passed; git diff --check passed. The correction changes only the audit document.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.7	Details Check Score Reason Code-Review 🟢 8 Found 21/24 approved changesets -- score normalized to 8 Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices 🟢 5 badge detected: Passing Pinned-Dependencies 🟢 5 dependency not pinned by hash detected -- score normalized to 5 Fuzzing 🟢 10 project is fuzzed Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Packaging 🟢 10 packaging workflow detected Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 17 contributing companies or organizations Vulnerabilities ⚠️ 0 45 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.7	Details Check Score Reason Code-Review 🟢 8 Found 21/24 approved changesets -- score normalized to 8 Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices 🟢 5 badge detected: Passing Pinned-Dependencies 🟢 5 dependency not pinned by hash detected -- score normalized to 5 Fuzzing 🟢 10 project is fuzzed Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Packaging 🟢 10 packaging workflow detected Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 17 contributing companies or organizations Vulnerabilities ⚠️ 0 45 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.7	Details Check Score Reason Code-Review 🟢 8 Found 21/24 approved changesets -- score normalized to 8 Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices 🟢 5 badge detected: Passing Pinned-Dependencies 🟢 5 dependency not pinned by hash detected -- score normalized to 5 Fuzzing 🟢 10 project is fuzzed Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Packaging 🟢 10 packaging workflow detected Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 17 contributing companies or organizations Vulnerabilities ⚠️ 0 45 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.7	Details Check Score Reason Code-Review 🟢 8 Found 21/24 approved changesets -- score normalized to 8 Dependency-Update-Tool 🟢 10 update tool detected Maintained 🟢 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy 🟢 10 security policy file detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege License 🟢 10 license file detected Binary-Artifacts 🟢 10 no binaries found in the repo CII-Best-Practices 🟢 5 badge detected: Passing Pinned-Dependencies 🟢 5 dependency not pinned by hash detected -- score normalized to 5 Fuzzing 🟢 10 project is fuzzed Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Packaging 🟢 10 packaging workflow detected Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 17 contributing companies or organizations Vulnerabilities ⚠️ 0 45 existing vulnerabilities detected

Scanned Files

• agent-governance-antigravity-cli/package-lock.json
• agent-governance-claude-code/package-lock.json
• agent-governance-copilot-cli/package-lock.json
• agent-governance-copilot-cli/package.json

[github-actions]

PR Review Summary

Check	Status	Details
🔍 Code Review	⚠️ Missing	No current-run comment
🛡️ Security Scan	⚠️ Missing	No current-run comment
🔄 Breaking Changes	⚠️ Missing	No current-run comment
📝 Docs Sync	⚠️ Missing	No current-run comment
🧪 Test Coverage	⚠️ Missing	No current-run comment

Verdict: ⚠️ AI review incomplete; ready for human review

AI review comments are untrusted advisory output. The summary reports workflow-generated completion status only, not model-authored pass/fail claims.

[github-actions]

📦 Dependency diff (SBOM)

Comparing main → chore/sdk-5-cli-packages.

Summary: ➕ 0 added · ➖ 0 removed · 🔄 3 bumped

🔄 Bumped

npm (3)

Package	From	To
%40microsoft/agent-governance-antigravity-cli	4.0.0	5.0.0
%40microsoft/agent-governance-claude-code	4.0.0	5.0.0
%40microsoft/agent-governance-copilot-cli	4.0.0	5.0.0

[github-actions]

🔴 Contributor Check: HIGH

Check	Result
Profile	HIGH
Credential	LOW
Overall	HIGH

Automated check by AGT Contributor Check.

[Prayag (prayagupa)]

Correctly consolidates the three semver-major SDK bumps (#3686/#3681/#3683) byte-identical plus the required audit doc; all checks green. Note the carried-forward js-yaml advisory (GHSA-pm4m-ph32-ghv5, patched in 5.2.2) — durable fix is repinning js-yaml in the SDK. LGTM.

[Imran Siddique (imran-siddique)]

MohammadHaroonAbuomar liamcrumm — gentle nudge when you have a moment. This is the SDK 5.0.0 dependency update across the CLI packages, including the audit notes.

[Imran Siddique (imran-siddique)]

Prayag (@prayagupa) your approval from 08-12 was dismissed automatically when I merged main in on 08-19 to clear the stale-branch block. The PR's own diff is unchanged: same 9 files, +139/-34, and the merge only picked up main's additions to .cspell.json and .cspell-repo-terms.txt. Sorry for the churn. Would you mind re-approving?

[Prayag (prayagupa)]

Thanks — the diagnosis of why #3686, #3683 and #3681 can't satisfy the audit gate on their own branches is correct and worth landing.

One blocker: the doc reads the SDK's declared js-yaml, but the resolved version is 4.2.0 at base and head — so both 4.x HIGH advisories remain and GHSA-pm4m-ph32-ghv5 doesn't apply.

Separately, build-npm for agent-governance-antigravity-cli skipped (no pkg-agent-governance-antigravity-cli paths-filter), so it got no build validation here.

[Imran Siddique (imran-siddique)]

Prayag (@prayagupa) you are right, and I have pushed the correction rather than argued it. Thank you for not just re-approving when I asked you to.

Your blocker, verified

I reproduced it rather than reasoning about it. npm ci in agent-governance-antigravity-cli at this branch's head, then npm ls js-yaml:

@microsoft/agent-governance-antigravity-cli@5.0.0
`-- @microsoft/agent-governance-sdk@5.0.0
  `-- js-yaml@4.2.0 overridden

npm audit on that same tree:

high  GHSA-52cp-r559-cp3m   range=>=4.0.0 <4.3.0
high  GHSA-5p4m-2wfm-xmqj   range=>=4.0.0 <4.3.1

So the installed parser is 4.2.0 at base and at head, both 4.x HIGH advisories remain in range, and GHSA-pm4m-ph32-ghv5 cannot apply because 5.2.1 is never installed. The document's central claim, that the bump exchanges two HIGH advisories for one, was wrong in the direction that flatters the PR. I read the SDK's declared pin and never checked what actually resolves.

Worse, the same document argued that "overriding js-yaml in three CLI lockfiles would be the wrong fix", while all three package.json files have carried exactly that override the whole time. I was writing about a tree I had not installed.

A second defect, which I found looking for yours

The regenerated lockfiles here dropped the root overrides block while package.json kept declaring it. On main the two agree:

main:  package.json overrides={'js-yaml':'4.2.0'}   lock.root.overrides={'js-yaml':'4.2.0'}
head:  package.json overrides={'js-yaml':'4.2.0'}   lock.root.overrides=None

The node_modules/js-yaml entry still pinned 4.2.0, so the installed tree was right and npm ci passed either way, which is exactly why 110 green checks said nothing. But the lockfile had stopped recording the reason for its own pin, and the next regeneration would have moved it. Restored in all three.

The sequencing you should know about

Jeff Stock (@jstock03)'s #3843, #3844 and #3875 move the override 4.2.0 to 4.3.1 in the antigravity, Claude Code and Copilot CLI packages. That clears both advisories above, and it is the change that actually improves the security position here. They touch the same package.json and package-lock.json files this PR does, so we conflict. I would land theirs first and rebase this one on top, since the SDK bump is a version-line alignment with no urgency and theirs is the advisory fix. Happy to be told otherwise.

What changed in this push

• The audit document's dependency and advisory sections rewritten around the resolved version rather than the declared one, with the npm audit output and the conflict with fix: update Antigravity js-yaml override #3843/fix: update Claude Code js-yaml override #3844/fix: update Copilot CLI js-yaml override #3875 recorded.
• The Breaking Change section corrected: the js-yaml 4.x to 5.x major is not reached at all, so the risk paragraph built on it was wrong too.
• The root overrides block restored in the three lockfiles.
• No change to the SDK bump itself. Still the same nine files, and the lockfile diff is three lines per package.

On your second point

build-npm skipping agent-governance-antigravity-cli for want of a pkg-agent-governance-antigravity-cli paths-filter is a real gap and it is not this PR's to fix, since the filter has been missing for every PR that has touched that package. I would rather it went in on its own so it is visible as a CI change. Say the word if you would prefer it here instead.

[MohammadHaroonAbuomar]

Approved after group integration review (tests, gates and adversarial pass on the combined change).

[MohammadHaroonAbuomar]

Prayag (@prayagupa) this one is verified and approved on my side; it's blocked only by your three unresolved threads (js-yaml audit wording, package.json overrides). Could you resolve them if you're satisfied with Imran's replies, or say what's still missing?

[MohammadHaroonAbuomar]

• docs/dependency-audits (the js-yaml section) says npm audit reports 'both, and no others'; since 2026-09-08 it reports a third HIGH on js-yaml 4.2.0, GHSA-2883-xcg3-v3hh (fixed in 4.3.2), so the sentence is now wrong — please update it, and note that #3843/#3844/#3875's move to 4.3.1 would not clear it either (only #3894's 4.3.2 does). Prayag's third thread (dropping the override from the three package.json files) still needs your reply in the thread itself; your rationale is only in the dc83a6e commit body.

[Imran Siddique (imran-siddique)]

MohammadHaroonAbuomar Prayag (@prayagupa) the requested audit corrections are in f1d399f. The residual-exposure paragraph now points to #3894's 4.3.2 override, the older audit observation is dated, the nonexistent output reference is removed, and last_reviewed is 2026-09-14. I also corrected the PR description and replied in each review thread, including Prayag's original override thread.

The three manifest/lockfile pairs still agree on the 4.2.0 override; the parser version fix remains in #3894 and should land first. Scoped docs checks passed locally, and the workflows on this head have completed without failures or held runs. Could you re-review the corrections and resolve the threads if satisfied?

[MohammadHaroonAbuomar]

Verified at e9b6c66: the SDK bump is limited to the three CLI package.json files and their lockfiles, which stay byte-identical after npm ci with js-yaml resolving to 4.2.0 under the kept override. The audit doc now agrees with itself and with the advisory data (three js-yaml advisories on 4.2.0, 4.3.1 clears two, #3894's 4.3.2 clears all three; the typescript pin history is 5.2.3 then 5.4.0). Merge commit 864e9de is a mechanical merge of main. CI green.