MCPcopy Index your code
hub / github.com/go-openapi/spec

github.com/go-openapi/spec @v0.22.6

Chat with this repo
repository ↗ · DeepWiki ↗ · release v0.22.6 ↗ · + Follow
562 symbols 1,615 edges 63 files 376 documented · 67% 183 cross-repo links updated 6d agov0.22.6 · 2026-06-14★ 4345 open issues
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

spec

Tests Coverage CI vuln scan CodeQL

Release Go Report Card CodeFactor Grade License

GoDoc Discord Channel go version Top language Commits since latest release


The object model for OpenAPI v2 specification documents.

Announcements

  • 2025-12-19 : new community chat on discord
  • a new discord community channel is available to be notified of changes and support users

You may join the discord community by clicking the invite link on the discord badge (also above). Discord Channel

Status

API is stable.

Import this library in your project

go get github.com/go-openapi/spec

FAQ

  • What does this do?
  1. This package knows how to marshal and unmarshal Swagger API specifications into a golang object model
  2. It knows how to resolve $ref and expand them to make a single root document
  • How does it play with the rest of the go-openapi packages ?
  1. This package is at the core of the go-openapi suite of packages and code generator
  2. There is a spec loading package to fetch specs as JSON or YAML from local or remote locations
  3. There is a spec validation package built on top of it
  4. There is a spec analysis package built on top of it, to analyze, flatten, fix and merge spec documents
  • Does this library support OpenAPI 3?

No. This package currently only supports OpenAPI 2.0 (aka Swagger 2.0). There is no plan to make it evolve toward supporting OpenAPI 3.x. This discussion thread relates the full story.

An early attempt to support Swagger 3 may be found at: https://github.com/go-openapi/spec3

  • Does the unmarshaling support YAML?

Not directly. The exposed types know only how to unmarshal from JSON.

In order to load a YAML document as a Swagger spec, you need to use the loaders provided by github.com/go-openapi/loads

Take a look at the example there: https://pkg.go.dev/github.com/go-openapi/loads#example-Spec

See also https://github.com/go-openapi/spec/issues/164

  • How can I validate a spec?

Validation is provided by the validate package

  • Why do we have an ID field for Schema which is not part of the swagger spec?

We found jsonschema compatibility more important: since id in jsonschema influences how $ref are resolved. This id does not conflict with any property named id.

See also https://github.com/go-openapi/spec/issues/23

Change log

See https://github.com/go-openapi/spec/releases

References

https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md

Licensing

This library ships under the SPDX-License-Identifier: Apache-2.0.

Other documentation

Cutting a new release

Maintainers can cut a new release by either:

  • running this workflow
  • or pushing a semver tag
  • signed tags are preferred
  • The tag message is prepended to release notes

Extension points exported contracts — how you extend this code

Core symbols most depended-on inside this repo

Shape

Function 250
Method 250
Struct 48
TypeAlias 13
Interface 1

Languages

Go100%

Modules by API surface

schema.go70 symbols
parameter.go35 symbols
swagger.go32 symbols
operation.go30 symbols
expander_test.go27 symbols
items.go24 symbols
header.go22 symbols
resolver_test.go19 symbols
validations.go18 symbols
expander.go17 symbols
info.go15 symbols
ref.go14 symbols

For agents

$ claude mcp add spec \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact

Ask about this repo answers extend the page