Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 22:27 UTC

getkin / kin-openapi

OpenAPI 3.0 and 3.1 and 3.2 (and Swagger v2) implementation for Go (parsing, converting, validation, and more)

GoMIT★ 3,274 stars⑂ 507 forkssince Jun 2017View on GitHub ↗
KindLibraryApplicationhow this is determined

getkin/kin-openapi holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (89/100) and lowest on Security (58/100). It was last updated 6 days ago. 2 contributors account for most of its recent work.

84
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

84
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 71 is calibrated to 84 on the published index scale (record calibration 2026-08-02).

Ownership

getkinOrganization
12 followers2 public repossince Jun 2018

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/getkin/kin-openapiv0.146.0-15010 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
16.6/36Commit cadence — 24/52 weeks with commits
18/18Commit volume — 184 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year184
human_commit_share1
days_since_last_push6
active_weeks_last_year24

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 10 days ago
27/27Release cadence — a release every ~10.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.146.0
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases10.8
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

69Good · 17% of overall
How it's scored
57/60Stars — 3,274 stars
22.5/25Forks — 507 forks
6.8/15Watchers — 18 watchers
Inputs used
forks507
stars3,274
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, pkg.go.dev
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.1/22.5Commit distribution — top contributor authored 42% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.417
How it's scored
33.1/42Issue resolution — 79% of issues closed
25.3/30PR acceptance — 636/754 decided PRs merged
13/13Newcomer PR acceptance — 6/6 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 16/29 approved changesets -- score normalized to 5
Inputs used
merged_prs636
open_issues101
closed_issues375
prs_merged_7d1
prs_decided_7d1
prs_merged_30d15
prs_decided_30d15
issue_closed_ratio0.788
closed_unmerged_prs118
first_time_authors_30d4
first_time_prs_merged_30d6
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
8/25Owner reach — 12 followers of getkin
15.5/25Track record — 2 public repos, account ~8 yr old
Inputs used
followers12
owner_typeOrganization
is_verified
owner_logingetkin
public_repos2
account_age_days2,978
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 10 days ago
20/20Version history — 150 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/getkin/kin-openapi
ecosystemsgo
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 20 out of 20 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsopenapi, openapi3, swagger, api, documentation, golang, hacktoberfest, openapi2
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 16/29 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 27 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages13
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 13 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

62Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.4/40Legible commit history — 72 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.72
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.17
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
54.2/55Manageable file sizes — 4/285 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes86,568
source_files_sampled285
oversized_source_files4
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — openapi2/testdata/swagger.json, openapi2conv/testdata/swagger.json, openapi3/testdata/issue1205/openapi.yml, openapi3/testdata/issue959/openapi.yml, openapi3/testdata/recursiveRef/openapi.yml, openapi3/testdata/refInLocalRef/openapi.json, openapi3/testdata/refInLocalRefInParentsSubdir/spec/openapi.json, openapi3/testdata/refInRef/openapi.json, openapi3/testdata/refInRefInProperty/openapi.yaml, openapi3/testdata/refsToRoot/openapi.yml, openapi3/testdata/relativeDocs/openapi/openapi.yml, openapi3/testdata/relativeDocsUseDocumentPath/openapi/openapi.yml
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesopenapi2/testdata/swagger.json, openapi2conv/testdata/swagger.json, openapi3/testdata/issue1205/openapi.yml, openapi3/testdata/issue959/openapi.yml, openapi3/testdata/recursiveRef/openapi.yml, openapi3/testdata/refInLocalRef/openapi.json, openapi3/testdata/refInLocalRefInParentsSubdir/spec/openapi.json, openapi3/testdata/refInRef/openapi.json, openapi3/testdata/refInRefInProperty/openapi.yaml, openapi3/testdata/refsToRoot/openapi.yml, openapi3/testdata/relativeDocs/openapi/openapi.yml, openapi3/testdata/relativeDocsUseDocumentPath/openapi/openapi.yml
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

3,274GitHub stars
100contributors
184commits, last 12 months
6days since last push
100releases
2bus factor
101open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 507 ⇿
0Stars
507Forks
100Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

010020030040050049772018-032022-062026-08
Major 0Minor 100Patch 0

Each point covers 8 days.

OpenSSF Scorecard 4.6 / 10
4.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-13 22:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 16/29 approved changesets -- score normalized to 5
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Gogithub.com/go-openapi/jsonpointerv0.22.5go.mod
Gogithub.com/gorilla/muxv1.8.0go.mod
Gogithub.com/oasdiff/yamlv0.1.1go.mod
Gogithub.com/oasdiff/yaml3v0.0.14go.mod
Gogithub.com/santhosh-tekuri/jsonschema/v6v6.0.2go.mod
Gogithub.com/stretchr/testifyv1.9.0go.mod
All dependencies 13

Full resolved dependency set from the GitHub dependency graph: 6 direct and 7 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogithub.com/go-openapi/jsonpointerv0.22.5direct
Gogithub.com/gorilla/muxv1.8.0direct
Gogithub.com/oasdiff/yamlv0.1.1direct
Gogithub.com/oasdiff/yaml3v0.0.14direct
Gogithub.com/santhosh-tekuri/jsonschema/v6v6.0.2direct
Gogithub.com/stretchr/testifyv1.9.0direct
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/go-openapi/swag/jsonnamev0.25.5indirect
Gogithub.com/kr/textv0.2.0indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogolang.org/x/textv0.14.0indirect
Gogopkg.in/check.v1v1.0.0-20201130134442-10cb98267c6cindirect
Gogopkg.in/yaml.v3v3.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 13 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/textv0.14.0indirectunknown10.39.0

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.