Repository navigation
Conversation
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.
Several integration package roots contained vulnerable dependency versions, and changing the MCP source invalidated the hosted bundle's reviewed-source binding. This PR updates compatible dependencies, rebuilds the hosted bundle from the reviewed source and lockfile, and tests the dependencies actually included in the artifact.
The remediation covers Claude SDK conformance, the OpenRouter review pack, MCP, the HyperFrames fixture, the Risk Fork live-demo and release roots, Interchange SAM, and the hosted MCP build root. Lockfiles were regenerated through npm; integrity values were not fabricated. The OpenRouter changes also appear in the still-open standalone #520.
The hosted bundle now includes Zod 4.6.7 and fast-uri 3.1.9. Its build dependency tree contains MCP SDK 1.32.0, Hono 4.13.13, body-parser 2.4.0, ip-address 10.7.4, and qs 6.16.1. These build dependencies are distinct from the MCP source package's own dependency graph. The integrity manifest binds the actual selected package bytes; embedded package metadata alone is not used as proof of the bundled version. A new regression rejects stale Zod package bytes even when the attested inventory still describes the patched package.
The exact package contracts in the builder and verifier remain enforced. Reviewed-source refresh was explicit. The optional E2B peer, default-off provider boundary, disabled publishing hook, and runtime authority checks remain intact.
Validation performed in the isolated build worktree:
08f3ebc4dafb44881dc4bdc86723ff6703c3822446d4cf9b75aa8ef2f6d1ff19The complete test counts above were observed by the implementation agent; separate stdout files were not retained for every run. A separate reviewer reproduced the hosted tests, MCP pin tests, source/artifact verification, and reproducibility check, and found no remaining actionable issue in this bounded dependency/integrity repair. The coordinator independently verified actual Zod input hashes, registry integrity, and the full hosted audit. This is agent source review, not formal independent human approval.
Current reviewed head:
1eab920cd6931b1ed61e114a6b751d08f24bec86. Final hosted CI: 29 passing checks, one failure, zero skipped or pending checks. PostgreSQL authority passed all 70 tests with zero failures/skips; all three managed-service matrix jobs passed. The one failed job still skips its later validation steps as explained below.The PostgreSQL service now pulls from the official Docker Hub registry using exactly the prior immutable digest. The two OCI index responses from ECR and Docker Hub were byte-identical (10,237 bytes; SHA-256
ca0bd484cb98bf4b24eb1010e73fb3fcbd6714d240fbc1a10eea5b7dbecb641d). Both service references changed; all TLS, mandatory tests, service configuration, matrices, permissions and health checks remain intact. An independent agent reviewed this diff and registry proof. This addresses the ECR download quota failure without selecting a mutable tag or another build. Anonymous registry availability remains an operational dependency.The remaining failure is Validate Machine Surfaces: the unchanged n8n development graph contains four high findings propagating one Zod advisory. Its eight tests, lint, build and production-only audit pass before the full audit correctly rejects the graph. Subsequent validation steps are skipped, not passes.
The n8n investigation traced actual consumers. Workflow 2.28.4 and expression-runtime 0.19.1 require exact Zod 3.25.67. Later inspected workflow 2.44.2/2.45.1 still require affected Zod 3.25.76. The current workflow's published declarations supply five arguments to
ZodObject; Zod 4's root type accepts two. npm's workflow 1.75.1 downgrade conflicts with the retained community plugin's workflow >=2 peer. Routing consumers tozod/v3preserves the type shape but does not inherit the official v4-only security patch. Neither a blind override, a plugin downgrade, nor a v3 alias was adopted. No n8n manifest or lock entry changed.n8n/TOOLCHAIN_AUDIT.mdand the README now distinguish historical clean audits from the current blocking result. Fresh full/production audit JSON and published consumer evidence are retained in the local evidence packet. Five local fail-closed audit-policy tests passed; schema/count/rename-inventory/whitespace checks passed. Independent source review found no material documentation issue. Preferred resolution is a compatible upstream patched release; a maintained consumer migration or backport needs a separate design/maintenance decision and behavioral/type/security qualification. This is a concrete compatibility limit, not a claim that migration is impossible.Final PostgreSQL evidence: authority job. The generated hosted bundle remains unchanged and its final-head job passes.
Keep this PR draft and unmerged until final-head CI and the repository's required independent approval are satisfied. #520 is not closed as superseded until this combined remediation is merged. #517 remains the separate Pillow remediation.
Dependencies were installed only in isolated build worktrees for validation. No package publication, owner-runtime installation, deployment, provider call, payment, credential creation, or live qualification occurred. Passing package tests do not establish a qualified hosted MCP, E2B, or production deployment.
Workflow trace: implementation agent
/root/integrations_bundle_repair; independent source/integrity reviewer/root/marketplace_final_review; PostgreSQL registry reviewer/root/integrations_bundle_repair; n8n consumer investigator/root/marketplace_final_review; documentation reviewer/root/memory_merge_verification; coordinator owns synthesis, commit, push, and CI verification. No governed ECF execution or human sign-off is claimed.