Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.0b3 instead.
Reason given by maintainers: placeholder version

fusedwasi

Header-only C host for the WASI Component Model, for core modules fused from components (wasm2c and other C hosts), with a Python twin.

Placeholder: nothing is released yet. What follows is the idea and the shape of the API, taken from the code that is to move here (the WASI 0.2 host of wasmext: c/p2/*.h and p2/*.py).

The idea

A tool such as meld fuse turns a composed component into one core module: a memory for each component, the adapters between them are plain wasm, and the imports are the flat core form of wasi:* functions. Such a module needs only a host that implements those imports. fusedwasi is that host and nothing else: no engine, no component parser, no canonical ABI between components (the fuse already built it in).

flowchart TB
    subgraph build["1. Build"]
        direction LR
        C1["component A<br/>(any language)"] --> F["meld fuse<br/>(or unbundle)"]
        C2["component B"] --> F
        F --> M["one core module<br/>memory per component<br/>imports wasi:*@0.2"]
    end

    subgraph run["2. Run"]
        direction LR
        H["C host (.h)<br/>wasmext, other C hosts"] --> FW
        Y["Python host (.py)<br/>wasmhost"] --> FW
        FW["fusedwasi<br/>state: handles, memories, hooks<br/>one function per import:<br/>cli · clocks · random · io · filesystem · sockets"]
    end

    build -- "AOT: wasm2c · runtime: any engine" --> run

AOT and runtime. The library asks the engine for two things only: the memory of each component (a base and a size) and a way to call a function for each import. So it does not matter how the module runs: compiled ahead of time to C with wasm2c (the C headers are included into the generated glue, nothing is needed at run time), or in an interpreter or a JIT that calls the same functions through its import table (the C headers from an embedder, the Python twin from a Python host). Only the AOT route has been run so far (wasmext, wasm2c); the runtime route follows from the interface and is not tested.

The API (planned; the shape of the current code)

One state, one flat function per import, the same names and arguments in C and in Python. The host gives the state what it decides (arguments, preopened directories, which sockets are allowed, the standard streams, a trap); the rest is the library.

#include "wasi_p2_cli.h"             /* or wasi_p2_filesystem.h, wasi_p2_sockets.h, ... */

wasi_p2_state s;
wasi_p2_init(&s);                    /* defaults: system clocks, /dev/urandom, nothing allowed in sockets */
s.args = args, s.arg_count = 2;
s.realloc = my_cabi_realloc;         /* the cabi_realloc of component `comp` */
s.trap = my_trap;                    /* in a wasm2c module: wasm_rt_trap */
wasi_p2_set_memory(&s, 0, base, size);       /* once for each component; set again when the memory grows */

/* the body of an import of the module: the first argument is the component whose memory it is */
wasi_cli_environment_get_arguments(&s, /*comp*/ 0, /*retptr*/ ptr);
from fusedwasi import Host, wasi_p2_cli as cli     # the module names follow the C headers

host = Host([memory], args=["prog"], realloc=my_cabi_realloc)   # a memory is any writable buffer
cli.wasi_cli_environment_get_arguments(host, 0, ptr)
Part What the host gives What the library does
memory a base and a size for each component checked, little-endian loads and stores; a pointer outside is a trap
handles nothing the table of own and borrow (generation + index), [resource-drop]
lists and strings it returns realloc (the cabi_realloc of the component) placing them in the guest's memory
files the preopened directories (path, name, writable) paths confined below the preopen (POSIX)
sockets socket_addr_check, allow_ip_name_lookup; refused by default TCP, UDP, name lookup (POSIX)
time, random, exit, wait a hook, or the system's own the rest

Every function is static inline and nothing is global or thread-local, so a module links only what it imports and several instances can live in a process.

Who uses it

  • wasmext (C, through wasm2c): the glue of a module includes the headers; no Python at run time.
  • wasmhost (Python): the twin in .py under the engines it supports.
  • Any other host that can give a memory and call a function for each import.

Not here

Components made of components (the fuse does that), WASI 0.3 and async, an engine, a parser of WIT.

Metadata

Release files for fusedwasi 0.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fusedwasi 0.0.0
File Size Uploaded Provenance Actions
fusedwasi-0.0.0.tar.gz 3.0 kB With provenance Details for fusedwasi-0.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fusedwasi 0.0.0
File Interpreter ABI Platform Actions
fusedwasi-0.0.0-py3-none-any.whl Python 3 none any Details for fusedwasi-0.0.0-py3-none-any.whl

Total release size: 6.4 kB

Release files / fusedwasi-0.0.0.tar.gz

Download URL fusedwasi-0.0.0.tar.gz
Size 3.0 kB
Tags Source
SHA-256 checksum
How to use checksums
9de080af200ae315e404e40178423b47d2ae1f74d5c81f45f986c8dbe3dfafdd
BLAKE2b-256 checksum
How to use checksums
a3433c23f3bbbc24a59a5e64e376ada8294e3e896e5a299712e012b02aebff77
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Release files / fusedwasi-0.0.0-py3-none-any.whl

Download URL fusedwasi-0.0.0-py3-none-any.whl
Size 3.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
81e8da587e7c6b9727ffcb8fb3a01bf8f8bc26809d2f670db1f9949d05868868
BLAKE2b-256 checksum
How to use checksums
5e8ef35ba4b1107de9e135f3bbe19799ce2e77167580b0298e4eb1f0879a96d0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Security for fusedwasi 0.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for fusedwasi-0.0.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page