Ecosystem map

Each Interlace product has its own site, its own release schedule and its own evidence files. They share a look and a docs layout, but you install and upgrade each one on its own.

The products today

ESLint plugins (eslint-plugin-*)

ESLint plugins that find security bugs, accessibility problems and framework mistakes in JavaScript and TypeScript, including code written by AI assistants. Each plugin is tested against a set of real code samples and compared with the existing plugins in its category.

These are unscoped packages — ESLint resolves plugins by the eslint-plugin-<name> convention, so putting them behind the @interlace/ prefix would break config resolution. The one scoped ESLint package is @interlace/eslint-devkit, the toolkit we author the plugins with.

• Read: eslint.interlace.tools
• Sample plugins: eslint-plugin-jwt, eslint-plugin-mongodb-security, eslint-plugin-react-a11y, eslint-plugin-vercel-ai-security

burgee

A CLI framework for Node.js. Everything a CLI needs that isn't your CLI. Written once, served to humans and agents alike.

You declare a command once, and burgee builds its help text, --json output, --schema, an MCP server, shell completions and TypeScript types from that one declaration. Coming from commander or yargs, npx burgee migrate rewrites the imports for you.

npm install burgee

• Read: burgee.interlace.tools
• Source: github.com/ofri-peretz/burgee

Serverless plugins (@interlace/serverless-*)

Plugins for the Serverless Framework on AWS, written in TypeScript as replacements for popular community plugins. Remove one and it deletes what it created, so nothing keeps billing you.

• Read: serverless.interlace.tools
• Sample plugins: @interlace/serverless-api-gateway-caching, @interlace/serverless-iam-roles-per-function, @interlace/serverless-devkit

Interlace UI (@interlace/ui)

The React design system every Interlace site is built with: components, page blocks, layout templates, and the design tokens (colour, type, spacing) that keep the sites looking alike.

It ships as a shadcn-compatible registry, not an npm package. You copy components into your own repo and own them, with no version lock and no runtime dependency on us:

npx shadcn@latest add https://ds.interlace.tools/r/button.json

Every component carries the same floor: axe-clean, dark mode, RTL, and keyboard support, all verified in CI against every story.

• Browse + install: ds.interlace.tools
• See every state: storybook.interlace.tools

How they relate

Every product follows the same three rules:

• Numbers you can check — every comparison cites a versioned benchmark you can rerun.
• One way to read the docs — same theme, navigation and components on every site.
• Few dependencies — each one is there for a reason we can state.

That is what the Interlace name promises. The npm name follows whatever the ecosystem expects — unscoped for ESLint plugins, @interlace/ for everything else — but the guarantees are the same either way.

Adding new products

The line is intentionally small today. Future products will appear here when they ship, not before — every product on this page has a measured corpus, a real user, and shipped releases.

If you have a use case Interlace doesn't cover yet, the best signal is to open an issue against an existing product asking for what's missing. The roadmap follows demand.