Linux workstation

Upstream software project

wasmedge

standalone runtime for WebAssembly

About wasmedge

standalone runtime for WebAssembly

This project links 3 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Debian 13 (Trixie): 3 package records. Catalog coverage diagram, not an application screenshot.wasmedge: recorded package coverageDebian 13 (Trixie)3 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
wasmedge
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-13
License expression
Not reported
Metadata completeness
95/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

standalone runtime for WebAssembly (C API shared library)

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 13 (Trixie)

  1. libwasmedge0

    Debian 13 (Trixie) / libs / source wasmedge

    0.14.1+dfsg-3.1

    standalone runtime for WebAssembly (C API shared library)

    amd64arm64trixie
  2. libwasmedge-dev

    Debian 13 (Trixie) / libdevel / source wasmedge

    0.14.1+dfsg-3.1

    standalone runtime for WebAssembly (development headers)

    amd64arm64trixie
  3. wasmedge

    Debian 13 (Trixie) / web

    0.14.1+dfsg-3.1

    standalone runtime for WebAssembly

    amd64arm64trixie

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.