EAOS public monorepo

EAOS public monorepo

Elevator Pitch

Plugin and application authors use EAOS to compose authorized features across server and browser hosts.

Why & Value

Four MIT foundation packages separate pure contracts, Server implementations, React clients and CLI tooling. Three generic MIT plugins provide approval, field customization and administration. Business plugins and production bindings keep their own ownership; public code never imports private implementations.

Key Highlights

@alneas/eaos-core: SDK, schemas and entitlement contracts
@alneas/eaos-server: HTTP/MCP, lifecycle, database and storage
@alneas/eaos-react: browser clients, workspaces and help
@alneas/eaos-cli: generation, diagnostics, baseline and release tools

Quickstart

Registry commands require an available release. Before publication, the owning workspace builds, tests and packs checksum-pinned tarballs for isolated consumers. app-core and react-tools remain external canonical dependencies.

Public import

Install the owning package and use the exact import in the example below. The subpath is not a separate npm package. Check the selected entry’s runtime and peer requirements in the linked architecture guide.

bun add @alneas/eaos-core

import { definePlugin } from '@alneas/eaos-core'

export const status = definePlugin({
  id: 'status',
  entitlement: { tier: 'public' },
  routes(router) {
    router.post('/ping', async () => ({ ready: true }))
  },
})

Next Steps