This repository is the official source of truth for the OpenAPI Specification (OAS), the industry-standard format for describing HTTP APIs. It is not a runtime application but rather a meticulously managed collection of specification documents, JSON Schema files, proposals, and the infrastructure tooling required to build, validate, and publish the specification. The repository's architecture is a monorepo for a standard, leveraging a shared build infrastructure package (`@oai/build-infra`) for tasks like markdown linting, HTML generation, and schema publication. Key entry points include the versioned specification files in `versions/`, the CI/CD workflows in `.github/workflows/`, and the governance documents. The primary data flow involves transforming Markdown specification sources into published HTML and JSON Schema artifacts. The repository demonstrates high craftsmanship in its governance model, branch management strategy (main/dev/release branches with automated syncing), and issue automation. It is actively maintained with a low technical drift risk, making it a model for how open standards should be managed. While the core content is a specification, the repository itself functions as an application of infrastructure tooling, with sophisticated CI/CD pipelines, test suites for schema validation and markdown rendering, and reusable scripts for branch management and issue lifecycle automation.
This repository is the official home of the Model Context Protocol (MCP), an open standard defining how AI assistants discover and invoke external tools, resources, and prompts over JSON-RPC. In production it operates as a specification and governance hub: versioned TypeScript protocol schemas (2024-11-05 through 2026-07-28 plus draft) are compiled into JSON Schema artifacts, human-readable specification docs are generated and published, and a SEP (Specification Enhancement Proposal) process is automated by a GitHub bot that detects proposals, enforces lifecycle transitions, pings authors, and sends Discord notifications. The architecture is not a monolithic service or microservices; it is a mixed content-plus-tooling repository. The primary code components are the TypeScript schema sources, the schema/doc generation scripts (scripts/generate-schemas.ts, scripts/render-seps.ts), and the sep-automation Node.js application (tools/sep-automation), which uses explicit interfaces for the GitHub client, hooks, and workflow rules. Core data flows are: TypeScript interfaces -> JSON Schema -> published schema files and examples; SEP markdown -> rendered MDX documentation; and GitHub issue/PR events -> SEP state machine -> comments and Discord webhooks. External dependencies include Octokit/GitHub App auth, Discord webhooks, TypeDoc/typescript-json-schema, Mintlify for docs, and Hugo for the blog. Although classified as an application repo because of its runnable tooling, CI/CD, and unit tests, the dominant character is an open-standards documentation and governance project. It is actively maintained, enforces a conformance-testing mandate for SDKs, and contains well-crafted modular code. The main risks are content-version overhead (six dated spec snapshots plus draft, duplicated docs, frozen historical SEPs) and process/doc drift, not software decay.
This repository maintains the HTML Living Standard, the definitive specification for HTML. It processes a Wattsi-formatted source file to generate the HTML specification in multiple formats (single-page, multi-page, and developer's edition). The repository includes automated build and deployment workflows, comprehensive documentation (FAQ, contributing guidelines), and interactive demos showcasing HTML features. Key reusable components include a variable highlighting utility for algorithms, image processing filters, a find-as-you-type search implementation, and a definition lookup panel. The project is actively maintained with recent commits and employs modern web technologies throughout its tooling and demos.
This repository is the official open-source implementation of the Matter smart home connectivity standard, developed by the Connectivity Standards Alliance. It provides a comprehensive SDK for building Matter-compliant devices (e.g., lighting, locks, thermostats, sensors) and controllers (e.g., smartphone apps, hubs). The codebase is a large, multi-platform C++ project with a layered architecture: a data model layer defining over 100 clusters (OnOff, Temperature, DoorLock, etc.), an interaction model for read/write/execute/invoke, a transport layer supporting BLE, TCP, and UDP, a security layer for certificate-based attestation and encryption, and a platform abstraction layer for numerous embedded MCUs (ESP32, nRF, Silicon Labs, NXP, etc.) and operating systems (Linux, Android, iOS, Zephyr, FreeRTOS). The SDK includes example applications for device types, reference controller tools (chip-tool, darwin-framework-tool, Android/Kotlin controllers), and extensive test infrastructure. Key entry points are the example app main.cpp files, the chip-tool CLI, and the Python command-line tool. Primary data flows involve commissioning (pairing a device via BLE or network, then establishing secure IP communication) and ongoing cluster interactions (attribute reads/writes, command invocations, event subscriptions). The build system is GN (Google's ninja) with platform-specific overrides, and code generation via ZAP for cluster definitions. External dependencies include OpenThread, BoringSSL, mbedTLS, Pigweed, nlassert, and others. The project is actively maintained with frequent commits, but the sheer number of example apps and platform ports creates maintenance overhead and some duplication.
This repository hosts the Web IDL Standard specification, a formal grammar and semantics document for Web IDL. It is primarily a Bikeshed source document (index.bs) that generates the official specification HTML. The repository includes a build pipeline (Makefile, GitHub Actions) that compiles the spec and runs a grammar validation script (check-grammar.js) to ensure the grammar is LL(1). While not a software application in the traditional sense, it contains tooling for specification maintenance and grammar verification. The codebase is minimal, with the core value being the specification text itself rather than reusable software components.
This repository contains the official Conventional Commits specification website, built with Hugo and a custom theme. It is a static documentation site with multi-language support (29 languages) across multiple specification versions (v1.0.0 and several beta releases). The site is deployed via Netlify with a Docker-based build pipeline. The codebase is primarily HTML/CSS/JS assets and Hugo layout templates, with no application logic, APIs, or data processing. The specification itself is the core content, presented as markdown files organized by version and language. While the theme demonstrates decent SCSS architecture and a language switcher, the overall codebase is simple and tightly coupled to the spec content, offering limited reusability beyond similar documentation sites.