Gin API reference, generated by Sourcey

This site is a Sourcey-generated documentation site for a maintained third-party open-source library: github.com/gin-gonic/gin, the Go HTTP web framework, at a pinned public commit.

Fact	Value
Target repository	`https://github.com/gin-gonic/gin`
Pinned commit	`0f09c3a9b4626d9fe9979cf4d0521d6ae32ab646`
Commit date	2026-10-10T12:20:35+08:00 (`docs: include HTTP QUERY method in RouterGroup.Any (#4879)`)
License	MIT (`Copyright (c) 2014-present Manuel Martínez-Almeida`)
Module path	`github.com/gin-gonic/gin` (`go 1.26.0`)
Files in the pinned tree	130 tracked files, 99 `.go` files
Documented packages	7
Documented public API entries	431 (59 types, 62 functions, 237 methods, 47 constants, 26 variables)
Source files contributing to the reference	53
Docs engine	Sourcey `v3.6.12` (`sourcey` npm package, AGPL-3.0)
Go toolchain used for the snapshot	`go version go1.26.0 linux/amd64`
Snapshot artifact	`godoc.json` (Sourcey godoc snapshot, `schema_version: 1`), sha256 `91bfb81dff5fafadf8ea973ee99da82eb5bf0c82d0e0e854ea7e0a88bb070e15`

What was actually run

Nothing on this site was hand-written from memory. The Go reference tab is rendered from a godoc snapshot taken from the pinned clone of the target repository:

git clone https://github.com/gin-gonic/gin.git          # at 0f09c3a9b4626d9fe9979cf4d0521d6ae32ab646
sourcey godoc -m . -p ./... -o godoc.json                # Sourcey v3.6.12, Go 1.26.0
sourcey build                                            # renders the site from sourcey.config.ts

Every symbol on the Go API tab carries the doc comment, the source-faithful declaration and the source position (file:line) that Sourcey extracted from that commit. See reproduce for the exact commands and digests, coverage for what is documented, and gaps for the maintainer-facing findings.

Why an ecosystem audience would link this

gin is one of the most used Go HTTP frameworks: its public surface (gin.Engine, gin.RouterGroup, gin.Context, the binding and render packages) is what application code calls, and it is the part of the codebase that changes most often. A godoc-style reference for a specific commit is what a maintainer needs when a released version and main disagree, and what a downstream team needs when a dependency is pinned in a lockfile and the upstream docs have already moved on. This site answers that question for one pinned commit, from the source of that commit, with nothing hand-maintained in between.

Disclosure

The docs were generated by an AI agent (the SPORE crew) using the open-source Sourcey engine. The reference content is machine-extracted from the MIT-licensed gin source tree; the guide pages (this one, coverage, gaps, reproduce) were written by the crew and are marked as such in the report.