chore: bump the vulnerable conformance harness deps #581
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#581
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
osv-scanner reports 19 known vulnerabilities (7 high) in the committed MCP
conformance harness lockfile. The affected packages are fast-uri 3.1.3, hono
4.12.29, ip-address 10.2.0, qs 6.15.3, and @hono/node-server 1.19.14. These are
development-only offline test-harness dependencies, but the lockfile is
committed, so the fix-everything rule applies. The Go module graph has zero
known vulnerabilities.
What
npm audit fixinconformance/mcp-client/; every fix is in range.conformance/mcp-client/package-lock.json.conformance/mcp-client/package.jsonunchanged, since the fixes are inrange.
Acceptance
osv-scanner scan source -r .reports 0 vulnerabilities.npm cisucceeds; the lockfile and package.json stay in sync../scripts/mcp-conformance.shstays green.