* feat(rust): read cargo-auditable dependencies from WebAssembly modules cargo-auditable embeds the same zlib-compressed `.dep-v0` JSON in a WebAssembly custom section for wasm32 targets, but inspect_rust_binary rejected every module as an unsupported target because only ELF, PE and thin Mach-O containers were recognized. Walk the section framing of version 1 core modules to locate the `.dep-v0` custom-section payload and the data section, where rustc keeps its constant /rustc/<hash>/ paths. Rust lookups now read one format-neutral layout, so native and WebAssembly images share a single dependency-section owner. WebAssembly declares no container word size, so `bits` is null for that format only; the Evidence subject format is `file`, as for inspect_wasm_artifact. Truncated sections, invalid LEB128 sizes, custom-section names that run past their section or are not UTF-8, duplicate `.dep-v0` sections and a second data section are malformed. Components, such as wasm32-wasip2 output, embed core modules and are refused as unsupported, like universal Mach-O containers, rather than inspected through one selected module. * fix(rust): bound the WebAssembly section walk The WebAssembly reader visited every section synchronously, and the format sets no section count. A 256 MiB input of three-byte custom sections with empty names walked about 89 million sections and held the event loop for about 7.4 seconds, delaying cancellation and other MCP requests; empty type sections took about 1.9 seconds. Refuse a module with more than 65,536 sections with a typed cpu resource constraint that reports maximum_wasm_sections, as the Go header search reports its work budget. Producer output holds a few dozen sections, and the same inputs are now refused within tens of milliseconds. * fix(rust): accept WebAssembly Evidence in retained dependency views Retained Rust views compared the parent subject with a Mach-O-only format mapping, so WebAssembly Evidence, whose subject format is file, was refused as a different artifact. The report domain now owns the subject format next to the architecture mapping, and the service and the view both use it. The real CLI/MCP view workflow now also covers a WebAssembly module. * fix(rust): name the WebAssembly section-walk allowance in recovery Fixed-allowance recovery mapped every Rust resource other than capacity and transport to the parser allowance, so the section-walk refusal said host memory does not raise it. Each Rust resource now maps to its own allowance, and the cpu bound is a fixed work allowance. The MCP error contract test checks that the refusal is not retryable and names that allowance. * fix(rust): require WebAssembly container facts in reports The report schema tied a null word size to WebAssembly, but it accepted a wasm report that named a native architecture or big-endian byte order, and a native report that named the wasm architecture. Retained views parse imported Evidence with this schema, so such a contradictory report was accepted. The architecture is now wasm exactly when the container is WebAssembly, and a WebAssembly report must be little-endian. * docs(rust): record the WebAssembly dependency-metadata feature Feature work now carries a spec, plan and task list under docs/specs. This adds that record for reading cargo-auditable metadata from WebAssembly core modules and indexes it. The record states that it was written during review and lists the verification that remains open. * fix(rust): bind section names to containers and share the LEB128 reader The report schema accepted a dependency section name that does not belong to the report's container, such as a WebAssembly report naming the Mach-O section. rustDependencySectionName now owns that name for the reader and the schema, which refuses a mismatch for every container. The WebAssembly reader decoded section sizes with its own loop. It now uses the shared readLeb128, and an integer cut off by the end of the file is truncated rather than malformed. * fix(rust): classify a cut-off WebAssembly integer by its boundary The reader called an unfinished LEB128 integer truncated whenever its limit equalled the file length. A name length cut off inside the final section was therefore truncated, and the same bytes followed by another section were malformed. Each caller now states whether the file or the enclosing section bounds the integer. * fix(rust): report a duplicate WebAssembly dependency section first The section walk kept two .dep-v0 matches but walked on, so a module with two dependency sections and more than 65,536 sections after them was refused for the section bound instead of the duplicate it had already established. The walk now ends at the second match. * test(rust): assert WebAssembly container facts instead of limitation prose The CLI acceptance test matched an English limitation sentence. It now checks format, architecture, bits and byte order on the parsed report. * fix(rust): state container word size as 32 | 64 | null Output contract: inspect_rust_binary bits, including the summary view, is 32 | 64 | null. Null is valid only for WebAssembly and is not a number. ELF, PE and Mach-O reports stay 32 or 64. The schema description, guide, feature record and skill state that, and CLI renderers keep null instead of substituting a word size. --------- Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com>
2.6 KiB
Implementation plan
Boundary and contract
src/rust/RustWasmImage.ts owns WebAssembly section framing: the preamble,
layer and version, section sizes read with the shared readLeb128,
custom-section names, the .dep-v0 payload ranges and the data-section range. It reports failures through the
ParseFailure algebra with format wasm, and the section bound as a
max_wasm_sections decode limit.
src/rust/RustBinaryImage.ts builds one layout for either container: identity
facts, the dependency span and the spans searched for compiler paths. The
native layout comes from readBinaryContainer; the WebAssembly layout comes
from RustWasmImage. The dependency decoder, PE alignment allowance and rustc
path retention are shared and unchanged.
src/domain/rust/rustBinary.ts owns the report contract: format gains
wasm, and bits is explicitly 32 | 64 | null. Null is valid only when
format is wasm and is not a number. Refinements bind bits,
architecture, byte_order and the dependency section name to the container.
rustDependencySectionName is the one owner of that name for the reader and
the schema. metadataReportSubjectFormat in
src/domain/apple/machoTargetSelection.ts maps a wasm report to the file
subject, and requireMetadataReportSubject accepts it, so the service, the
retained views and the CycloneDX view agree on one mapping.
src/rust/RustBinaryProvider.ts projects the section-bound limit with
parseLimitConstraint as a cpu constraint and a fixed work ceiling, and
names the searched compiler-path source in limitations.
Incremental work and validation
- Walk section framing with boundary tests over synthetic modules.
- Read
.dep-v0and data-section rustc paths through the shared layout, and widen the report contract. - Bound the section walk after review showed a 256 MiB module of three-byte sections kept the synchronous walk busy for seconds.
- Map the Evidence subject once and run the retained-view workflow on a module.
- Bind the remaining container facts in the report schema.
- Update the guide, README rows, skill instructions, tool description and CLI
help, then run focused tests,
check,docs:checkand the source group.
Effects and compatibility
Output widening only: format gains wasm and bits is 32 | 64 | null
on the report and its summary view. Null is admitted only for wasm
reports, which were previously refused. ELF, PE and Mach-O reports remain
32 or 64. No new tool, input, subprocess,
temporary file or network access. Native reports change only in limitation
wording.