XIOM -- Ecosystem

Where the ecosystem stands

Layer	Status	Notes
Compiler	shipping	Releases on the mirror; v0.61.0 on main
Standard library	beta	Ships with the toolchain; 44 modules with published limitations
Registry	live (beta)	Browse and search today; publishing through publisher tokens
First-party packages	in porting	A large package corpus already exists in a monorepo; it was written against an earlier standard library and is being ported before anything is published
Community publishing	planned	Opens once the toolchain is stable and the registry leaves beta

We deliberately do not list packages that do not build against the current toolchain. This page describes the plan.

The plan

Stabilize the foundation. Compiler and standard library first -- a stable release is the prerequisite for everything else.
Port and publish first-party packages. The existing corpus is being ported to the current standard library; each package is published only when it builds, tests and carries contracts.
Open community publishing. The registry already enforces immutable versions, sha256 integrity and ed25519 signatures; publishing opens wide once the foundation is stable.
Graduate to per-package repositories. The monorepo is the working method; as packages mature they move to their own repositories under the xiom-lang organization.

Directions we are building toward

Categories, not product names -- specific packages are published when they are ready.

Data and storage

Typed embedded storage, query and vector search built on XIOM types and contracts -- no SQL strings, no ORM.

planned

Networking and web

HTTP clients and servers, serialization formats and protocol libraries with contract-checked boundaries.

planned

AI and machine learning

Tensor and numeric libraries, inference primitives and tokenizers, with contract-verified shapes and dimensions.

planned

Scientific computing

Linear algebra, statistics and plotting -- with FFI backends where the wider ecosystem is stronger.

planned

Graphics and games

GPU bindings and a game framework, leaning on the WebAssembly target for the browser.

planned

Systems and tooling

Editors, formatters, package tooling and generators that treat contracts as first-class documentation.

planned

Interoperability and bridges

Generators and bindings that bring C, C++ and Python libraries across the boundary, with ownership and contracts stated at the call site.

planned

Verification and analysis

Property testing, fuzzing and verifier frontends built on the contract and SMT path the compiler already exposes.

planned

Toolchain

The companion tools ship in every release archive: formatter, language server, documentation generator, package manager, debugger, verifier, foreign-interface generator and the MCP server for AI agents. See the compiler guide for the full tool surface.

Registry

The package registry is live at registry.xiom-lang.org. Browsers get a read-only UI: the package list, search, and version pages with digests, signatures and yank state, plus copy-ready install and trust commands. The same data is available as JSON at /index.json.

Client installs verify the sha256 of every artifact against the index, published versions are immutable, and first-party packages are signed with ed25519. Publishing is open through publisher tokens: request one via the publishing guide, and see the registry guide for install, locking and trust commands.

The service is in beta and the public package list is just beginning. The organization lives on GitHub: github.com/xiom-lang.