Built on these packages
These are reference applications rather than customers: five things that run on the collection, listed with what reading each one is worth and how deep into the set it goes. Two of them have no deployment, and say so.
uptime
32 packagesMonitors that check a URL on a schedule and say what they saw.
The widest reader of the collection: scheduled jobs, rate limits, billing, mail, feature flags and a full marketing site, all on the same set.
auth-saas
32 packagesSource onlyA multi-tenant OpenID Connect provider, a tenant to a Durable Object.
What the security packages look like under load: JWTs, passkeys, SAML, signed webhooks and per-tenant storage composed into one provider.
reader
29 packagesSource onlyA feed reader that subscribes, polls and pushes what it finds.
Every feed format in the collection read by one app — RSS, Atom, JSON Feed and OPML — alongside WebSub, caching and article extraction.
blog
23 packagesThe author's own site, its articles written in markdown.
The content pipeline end to end: markdown to a typed AST, syntax highlighting, feeds, sitemaps and the SEO tags around them.
books
13 packagesA reading log, kept small on purpose.
The smallest complete application here, and the shortest read: what an app needs from the collection before it needs anything else.
Each count is that application's @sdxc/* dependencies, read from its own package.json. Every package's reference page names which of these five install it, read from the same files.