Composed Swift building blocks for production systems — Layer 4 of the Swift Institute ecosystem.
Packages that compose the lower layers into working systems: HTTP and networking, markup and serialization, cryptography and authentication, database connectivity, I/O and filesystem, rendering, observability, and platform integration. Every package builds on swift-atoms (what must exist), swift-molecules (what is built from atoms alone) and swift-standards (specification implementations), and carries the same discipline throughout: typed throws end-to-end, strict memory safety, one repo per package.
| Package | What it gives you |
|---|---|
| swift-pdf | PDF document generation from HTML views and Markdown, authored with a result-builder DSL |
| swift-html | Type-safe HTML, CSS, and SVG generation, grounded in the WHATWG and W3C specifications |
| swift-file-system | Typed filesystem operations — scoped handles, atomic writes, zero-copy reads |
| swift-io-kernel | High-performance async I/O executor that isolates blocking syscalls from Swift's cooperative pool |
| swift-linter | SwiftSyntax-based AST linting with SARIF output |
The repositories tab lists every package with its description. Narrow it down:
http · html · css · svg · pdf · json · sql · render · logger · dependencies
Each package is a separate Swift Package Manager package with its own repository — there is no umbrella swift-compositions package:
dependencies: [
.package(url: "https://github.com/swift-compositions/swift-html.git", branch: "main")
]See each package's README for current products, traits, and platform support.
Public alpha. Packages are released repository by repository; APIs may change until first tagged releases.
Maintained by Coen ten Thije Boonkkamp — contributions welcome via pull request.
Packages use the Apache License 2.0, except the forks swift-sql and swift-sqlite, which keep their upstream MIT license.