# spec-first/connexion

Connexion is a modern Python web framework that makes spec-first and api-first development easy.

Repository: https://github.com/spec-first/connexion
Canonical: https://ross.abutalabs.com/products/connexion
Homepage: https://connexion.readthedocs.io/en/latest/
Language: Python
License: Apache-2.0
License Family: permissive
Topics: python, openapi, api-rest, swagger, flask-extensions, microservices, web, api-first
Last push: 2026-08-03T17:05:24+00:00

## Health v2 (maintenance only)
Score: 81/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 95, release rhythm 51, longevity 100
- inputs: {"age_days": 4124, "days_push": 30, "days_rel": 324, "gap_med": 9, "n_releases_24m": 4}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4611, forks 782 (observed 2026-08-28T04:08:54.994307+00:00)

## What it is
Connexion is a Python web framework for spec-first (API-first) development, where the API is described in an OpenAPI/Swagger specification that the framework enforces. It provides automatic routing, request/response validation, authentication, parameter injection, response serialization, a Swagger UI console, and a CLI for running and mocking specifications, working standalone or with any ASGI/WSGI framework.

## Use cases
- build a REST API from an OpenAPI spec
- validate request and response bodies against an OpenAPI schema
- auto-register routes from a swagger yaml file
- serve a Swagger UI console for my API
- mock an API from an OpenAPI specification
- add authentication to an OpenAPI-based API
- run a spec-first microservice in Python

## When to choose
- you design APIs contract-first with OpenAPI/Swagger and want the spec enforced at runtime
- you want automatic validation, routing, and docs from a single specification
- you need a framework that layers on top of existing ASGI or WSGI apps

## When to avoid
- you prefer code-first API development without maintaining a spec file
- you need a minimal framework with no specification overhead
- your API is not REST/HTTP-based or has no OpenAPI definition

## Facets
- artifact type: framework
- maturity: active
- function: web-framework, api-framework, auth, middleware, routing, serialization, mock-api, cli
- domain: web-development, backend, apis, microservices, developer-tools
- platform: python, cross-platform
- tags: openapi, swagger, spec-first, api-first, asgi, wsgi, request-validation, swagger-ui

## Member repositories
- spec-first/connexion (main) score 81

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:54.994307+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:19:43.535777+00:00, confidence not recorded.
  - readme: https://github.com/spec-first/connexion (fetched 2026-08-28T04:08:54.994307+00:00, sha 6e580daba2df)
  - registry_pypi: https://pypi.org/pypi/connexion/json (fetched 2026-08-29T09:05:20.170650+00:00, sha d396a59804e9)
- Data as of 2026-08-30T08:39:29.467469+00:00.
