Open Source Readiness

Stendar is currently developed in a private monorepo. Public launch work is staged: readiness happens first, then a later release phase decides which files, packages, and workflows are published.

This page is about readiness only. It does not mean the repository has already been split, npm packages have already been published, or desktop artifacts have already been released.

Candidate public surface

The first public surface is expected to center on SDK packages, curated no-secret examples, documentation, and contributor/security templates. Hosted API, billing, production infrastructure, deployment configuration, and private operational workflows remain private unless a future launch review explicitly moves them into scope.

Readiness checklist

Before any public split or package publish, maintainers should confirm every top-level path has a classification in OPEN_SOURCE_READINESS.md, public packages have package READMEs, examples work without live secrets, docs separate shipped behavior from roadmap direction, default CI avoids production secrets, vulnerability reporting is private, and package tarballs have been inspected with npm pack --dry-run.

Safety posture

Stendar is infrastructure software. It does not provide investment, legal, accounting, tax, brokerage, or custodial services. Examples and guides should default to simulation or dry-run behavior. Any live execution path must be explicit, approval-gated, and backed by local policy and audit controls.