microsoft/typespec
None observed · 2026-08-28
Health v2 · maintenance only
94/100
- Activity 99
- Release rhythm 85
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0
- age_days: 1890
- days_rel: 22
- days_push: 7
- n_releases_24m: 368
Adoption not part of the score
5832 stars · 387 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
TypeSpec is a Microsoft-built, extensible DSL and toolchain for defining cloud service APIs and data shapes as a single source of truth. It compiles TypeSpec definitions into OpenAPI 3, JSON Schema, Protobuf, client/server code, and documentation via an emitter framework, with editor extensions, a linter framework, and a formatter.
Use cases
- generate openapi spec from a single api definition
- define rest api schema once and emit multiple formats
- generate json schema for data validation
- design api contracts with reusable patterns and guardrails
- replace hand-written openapi yaml with a typed language
- generate protobuf definitions from api models
- lint api designs for anti-patterns
When to choose
- you maintain OpenAPI/JSON Schema specs across many services and want one source of truth
- you want reusable, versioned API design patterns enforced across teams
- you need to emit multiple API description formats from a single definition
When to avoid
- you have a single small API and a plain OpenAPI YAML file works fine
- your team has no appetite for learning a new DSL
- you need formats with no existing TypeSpec emitter
Facets
framework · maturity active
api-framework linter formatter serialization developer-tools apis web-development developer-tools documentation cross-platform cli editor-plugin api-design openapi json-schema protobuf dsl code-generation single-source-of-truth microsoft nodejs
8 sources
- readme: https://github.com/microsoft/typespec · fetched 2026-08-28 · 5dee0090184e
- homepage: https://typespec.io/ · fetched 2026-08-29 · 71f1bbad5b1f
- site_page: https://typespec.io/docs · fetched 2026-08-29 · 9578f1f74f6e
- site_page: https://typespec.io/docs/getting-started/typespec-for-openapi-dev · fetched 2026-08-29 · 7aaa4c78b5a5
- site_page: https://typespec.io/docs/extending-typespec/basics · fetched 2026-08-29 · a757b3122d2c
- site_page: https://typespec.io/openapi · fetched 2026-08-29 · 4158fd14763a
- site_page: https://typespec.io/data-validation · fetched 2026-08-29 · 6f0f60319415
- site_page: https://typespec.io/tooling · fetched 2026-08-29 · 91afb77a7126
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| microsoft/typespec | main | 94 |
For agents
markdown · JSON · MCP: product_card(name="microsoft/typespec")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem