go-openapi/analysis

GitHub: go-openapi/analysis

Stars: 35 | Forks: 45

# analysis [![Tests](https://static.pigsec.cn/wp-content/uploads/repos/2026/06/8e1bef2935021531.svg)][test-url] [![Coverage](https://codecov.io/gh/go-openapi/analysis/branch/master/graph/badge.svg)][cov-url] [![CI vuln scan](https://static.pigsec.cn/wp-content/uploads/repos/2026/06/9f9b9ca3ef021532.svg)][vuln-scan-url] [![CodeQL](https://static.pigsec.cn/wp-content/uploads/repos/2026/06/5e0a95fb08021533.svg)][codeql-url] [![Release](https://badge.fury.io/gh/go-openapi%2Fanalysis.svg)][release-url] [![Go Report Card](https://goreportcard.com/badge/github.com/go-openapi/analysis)][gocard-url] [![CodeFactor Grade](https://img.shields.io/codefactor/grade/github/go-openapi/analysis)][codefactor-url] [![License](http://img.shields.io/badge/license-Apache%20v2-orange.svg)][license-url] [![GoDoc](https://pkg.go.dev/badge/github.com/go-openapi/analysis)][godoc-url] [![Discord Channel](https://img.shields.io/discord/1446918742398341256?logo=discord&label=discord&color=blue)][discord-url] [![go version](https://img.shields.io/github/go-mod/go-version/go-openapi/analysis)][goversion-url] ![Top language](https://img.shields.io/github/languages/top/go-openapi/analysis) ![Commits since latest release](https://img.shields.io/github/commits-since/go-openapi/analysis/latest) A foundational library to analyze, diff, flatten, merge, and fix OAI specification documents for easier reasoning about the content. ## Announcements Or join our Slack channel: [![Slack Channel](https://a.slack-edge.com/e6a93c1/img/icons/favicon-32.png)![slack-badge]][slack-url] ## Status API is stable. ## Import this library in your project go get github.com/go-openapi/analysis ## What's inside * An analyzer providing methods to walk the functional content of a specification * A spec flattener producing a self-contained document bundle, while preserving `$ref`s * A spec differ ("diff") to compare two specs and report structural and compatibility changes * A spec merger ("mixin") to merge several spec documents into a primary spec * A spec "fixer" ensuring that response descriptions are non empty ## FAQ ## Change log See
标签:EVTX分析