Crypt in webassembly?

Just curious: go is a great language for crypt but it looks as if it is running as a coprocess, which seems a bit odd when everything else is running in javascript or browser compatible technologies. Instinctively, compiling the go to webassembly would mean that you could then run the crypt straight from inside nodejs, without platform specific portability issues. It just seems easier that way. I know it is easy to throw out suggestions but converting ideas into solid engineering is much harder work. If you explored webasm I would be interested in your perspective on this.

No file or test is identified. Start by locating the Go crypt coprocess and its Node.js or browser integration points, then evaluate whether a WebAssembly approach fits the existing architecture; done would be a documented feasibility assessment with a clear recommendation.

Written by the indexing model from the issue text.