Where the ecosystem stands
| Layer | Status | Notes |
|---|---|---|
| Compiler | shipping | Rolling releases on GitHub and the mirror; the versions page tracks the current tag |
| Standard library | beta | Ships with the toolchain; 44 modules with published limitations |
| Registry | live (2.x) | Publish, install and search, with sha256 checks, ed25519 signatures and provenance; GitHub sign-in, self-service grant requests, rendered READMEs and reviews, download stats, feeds and contributor profiles on top |
| First-party packages | shipping | Installable packages in the registry: see the registry, growing in batches as each package passes the build, test and contract gate |
| Community publishing | open (self-service) | Sign in with GitHub, then request a trusted-publisher entry or a publish token from the registry's Requests page; a maintainer approves it. Publishing stays signed (OIDC or token) -- a browser session can never publish |
| Playground | live | Browser compiler, lessons, the Algorithm Lab and its algorithm tiers at playground.xiom-lang.org; release phases are on the roadmap |
We deliberately do not list packages that do not build against the current toolchain; the registry is the live catalog. This page records what is published and what comes next.
How the ecosystem grows
The compiler, the standard library and the package corpus improve each other in a loop. The corpus is ported with AI assistance under review; the gates below, not the tooling, decide what publishes.
| Stage | What it receives | What it gives back |
|---|---|---|
| Compiler | Bugs found by package and language tests, with reproductions | Fixes and rolling releases; the toolchain every package gate pins |
| Standard library | Helpers that many packages re-implement, and missing modules | Shared modules adopted by batches of packages |
| Packages | Conformance suites on the pinned toolchain, and contract checks | Findings filed upstream and batches ready to publish |
| Registry | Packages that passed the gate, with signatures | Immutable signed versions, installs, reviews and yanks |
The loop is running now: package suites have already filed reproducible compiler bugs, and repeated helpers such as CRC and bit-reading code are tracked as standard-library work instead of staying as per-package copies. Nothing publishes that has not passed the gate.
What comes next
- More packages, in batches. The remaining corpus ships as each package passes the gates.
- More standard-library coverage. Repeated helpers become shared modules instead of per-package copies.
- 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 -- most of these already ship published packages, and the rest publish as they pass their gate.
Data and storage
Serialization and data-format packages are live on XIOM types and contracts -- no SQL strings, no ORM; typed embedded storage, query and vector search are the next layer.
shipping
Networking and web
Protocol and packet libraries are live with contract-checked boundaries; HTTP clients and servers are on the way.
shipping
AI and machine learning
Model and tensor file formats (GGUF, safetensors) and grammar files are live with contract-verified shapes and dimensions; numeric and inference libraries are the next layer.
shipping
Scientific computing
Domain and data formats are live (astronomy, chemistry, FITS, geospatial); linear algebra, statistics and plotting follow, with FFI backends where the wider ecosystem is stronger.
shipping
Graphics and games
Image, audio and video formats are live; GPU bindings and a game framework follow, leaning on the WebAssembly target for the browser.
shipping
Systems and tooling
System formats (ELF, GPT, device trees) and developer tools (diff, patch, flags, fuzzing) are live; more generators and editor tooling follow, treating contracts as first-class documentation.
shipping
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 SMT-LIB tooling are live on the contract path the compiler exposes; verifier frontends are the next layer.
shippingToolchain
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. The browser UI covers the package list, search, version pages with digests, signatures and yank state, rendered READMEs and reviews, download stats, an activity feed and contributor profiles, 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. The index itself is signed -- pin the key and an altered or rolled-back index is detectable -- CI publishes carry provenance naming the commit that built them, official packages are canaried on staging before they reach production, and versions cannot be swapped, downgraded or quietly deleted. Publishing opens with the GitHub sign-in: request a trusted-publisher entry or a publish token from the registry's Requests page, a maintainer approves it, and publishing stays signed and server-minted -- a browser session can never publish. The publishing guide covers the flow, and the registry guide covers install, locking and trust commands.
Official packages publish in batches from the release pipeline with signatures and provenance; the public catalog grows as each port passes its gate. The organization lives on GitHub: github.com/xiom-lang.