All blog posts
Updates 2 min read

Rust Test Vectors and Standards Tooling Replace JavaScript

Secure Net moved its shared test vectors, standards checks and manifest tooling into Rust before removing the original JavaScript implementation.

By Comutability Published Update from
Interlocking metallic gears with a globe motif illustrating Rust-based protocol testing and standards tooling.

Project update: 15 November 2026. GitHub change #13: merged into the repository. The underlying protocol remains draft and unaudited.

Secure Net moved its shared test vectors, standards checks and manifest tooling into Rust before removing the original JavaScript implementation.

Why we made this change

A programming-language transition is credible only when its replacement can test itself. Checking all protocol vectors in Rust provides stronger evidence that the new implementation describes the same wire formats, error handling and registries. Tools for manifests and standards then become part of the Rust development workflow.

The engineering record

The original pull request records the following technical scope and evidence. Some forward-looking notes in the record reflect the state of the work when the request was opened, rather than its status today.

The first stage of making Secure Net Rust-only. Before the JavaScript implementation can be removed, Rust must stand on its own against spec/vectors and the registries.

  • Every vector file is now checked by cargo test. tests/vectors_social.rs adds cvp-017, 018, 019 (v1 and v2), 020 and 021, which until now only the JavaScript checked.
  • secure-net-tools replaces scripts/manifest.mjs and scripts/standards.mjs. The manifest output is byte-identical. The standards check compares every registry entry with the Rust source, and I confirmed it catches a planted unregistered record kind and label. The documents it writes match the JavaScript output apart from the command name.
  • commons::EVENT_CAPS and extensions::EXECUTION are now public tables. The registry's suite entries point at Rust constants. CI runs the tools in the rust job.

Next stage: the npm package becomes the WebAssembly build. src/, the JavaScript tests, vectors.mjs and the JavaScript examples are removed, and the examples become Rust.

The wider direction

The Comutability approach is open source with human accountability. AI can help research, design, write code and test it, but a merged change is not the same thing as an independently audited product. Secure Net is explicitly described as a draft in its public README. Its use in a sensitive situation should wait for qualified cryptographic review.

What happens next

Preserve reproducible evidence and add cross-implementation tests from outside the project, not just tests written by the same team.

Read the original sources

Sources and further reading

Explore the evidence and original project records behind this article.