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

[Imran Siddique (imran-siddique)]

Consolidates #3686, #3683 and #3681, and adds the dependency audit that unblocks them.

Why they cannot land on their own

scripts/ci/vendored-patch-audit.sh exempts Dependabot only for non-major updates:

[ -n "$DEPENDABOT_UPDATE_TYPE" ] && \
[ "$DEPENDABOT_UPDATE_TYPE" != "version-update:semver-major" ]

These three run with DEPENDABOT_UPDATE_TYPE: version-update:semver-major, so the exemption does not apply and the gate requires an audit doc. It looks for that doc in the PR's own diff:

CHANGED_FILES=$(git diff --name-only "$BASE_REF"...HEAD)
AUDIT_DOC=$(grep -E '^docs/dependency-audits/[0-9]{4}-...' <<< "$CHANGED_FILES")

Dependabot does not write audit docs, so a semver-major Dependabot PR can never satisfy this gate on its own branch, and a separate doc PR would not satisfy it either. All three have been red on Dependency Audit Trail since 2026-08-11 for that reason, not because anything is wrong with them.

What this PR contains

The three Dependabot commits cherry-picked unchanged, plus one audit doc. Verified with git diff against each original head: package.json and package-lock.json in all three packages are byte-identical to what Dependabot produced. Their Signed-off-by: dependabot[bot] trailers are preserved, so authorship and DCO are intact.

bash scripts/ci/vendored-patch-audit.sh origin/main passes on this branch.

The finding worth reading

The audit is not a rubber stamp. This bump does not clear these packages of a js-yaml advisory.

• Outgoing js-yaml 4.1.1 is in range for two HIGH advisories: GHSA-5p4m-2wfm-xmqj (patched 4.3.1) and GHSA-52cp-r559-cp3m (patched 4.3.0).
• Incoming js-yaml 5.2.1, the SDK's own pin, is in range for GHSA-pm4m-ph32-ghv5, HIGH, >= 5.0.0, <= 5.2.1, first patched in 5.2.2. Current release is 5.2.3.

Two HIGH to one HIGH is the right direction and is not the same as clean. The durable fix is repinning js-yaml in the SDK rather than overriding it in three CLI lockfiles, so I have not attempted it here. Happy to open that separately if you want it.

Otherwise the risk is low. The SDK major is the monorepo-wide v5 version alignment from the [5.0.0] CHANGELOG entry, not an API break; the published 4.0.0 and 5.0.0 manifests agree on every @noble/* pin, on engines.node >=18.0.0 and on the license. Each of the three CLI packages already ships at 5.0.0 while pinning the 4.0.0 SDK, so this is the first time their published version and their SDK agree.

Suggested handling

Close #3686, #3683 and #3681 in favour of this, or tell me you would rather have three separate PRs each carrying its own copy of the doc and I will redo it that way.

[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.9	Details Check Score Reason Dependency-Update-Tool 🟢 10 update tool detected Security-Policy 🟢 10 security policy file detected Maintained 🟢 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 Code-Review 🟢 10 all changesets reviewed Dangerous-Workflow 🟢 10 no dangerous workflow patterns 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 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches Fuzzing 🟢 10 project is fuzzed Packaging 🟢 10 packaging workflow detected 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 50 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.9	Details Check Score Reason Dependency-Update-Tool 🟢 10 update tool detected Security-Policy 🟢 10 security policy file detected Maintained 🟢 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 Code-Review 🟢 10 all changesets reviewed Dangerous-Workflow 🟢 10 no dangerous workflow patterns 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 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches Fuzzing 🟢 10 project is fuzzed Packaging 🟢 10 packaging workflow detected 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 50 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.9	Details Check Score Reason Dependency-Update-Tool 🟢 10 update tool detected Security-Policy 🟢 10 security policy file detected Maintained 🟢 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 Code-Review 🟢 10 all changesets reviewed Dangerous-Workflow 🟢 10 no dangerous workflow patterns 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 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches Fuzzing 🟢 10 project is fuzzed Packaging 🟢 10 packaging workflow detected 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 50 existing vulnerabilities detected
npm/@microsoft/agent-governance-sdk	5.0.0	🟢 7.9	Details Check Score Reason Dependency-Update-Tool 🟢 10 update tool detected Security-Policy 🟢 10 security policy file detected Maintained 🟢 10 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 Code-Review 🟢 10 all changesets reviewed Dangerous-Workflow 🟢 10 no dangerous workflow patterns 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 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST 🟢 9 SAST tool detected but not run on all commits Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches Fuzzing 🟢 10 project is fuzzed Packaging 🟢 10 packaging workflow detected 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 50 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.