← all corpora

go-vulndb

reference corpus · status live · domain SEC (Security and vulnerabilities) · lane A · refresh weekly · tags GLOBAL · ADVISORIES · VULNERABILITIES · SECURITY

What an agent uses it for

an agent reviewing Go modules queries this for Go-team-curated advisories with symbols and fixed versions

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/go-vulndb.json
xerj corpus add --from ./go-vulndb.json
xerj corpus index go-vulndb then xerj code go-vulndb "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "go-vulndb", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
corpus-go-vulndb-osv 5cd8418cf9c8BSD-3-Clause 4.1 MB / 4,577 files 4577 flattened per-advisory text records from golang/vulndb data/osv/ @5cd8418cf9c867d344fda07a73ea844b0f34bca2 (BSD-3-Clause, LICENSE verified at pin; whole-repo provenance clone moved OUT of the corpus dir after it re-entered the walk). The previous pin 6f4f07681f45fbbc11cf2f1543d4222b51e7808d is rejected by golang/vulndb (git fetch: not our ref; GitHub commits API HTTP 422). G7 r2 4/5 (miss: qu

4.1 MB across 4,577 files. Added 2026-10-05.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

golang@golang · upstream

All contributors.

Rights

BSD-3-Clause. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

4.0/5 relevant. Graded .

Q: What could a malicious client forge through gin's URL handling per GO-2020-0001?
expect: corpus-go-vulndb-osv/go-2020-0001.txt
top-5: corpus-go-vulndb-osv/go-2020-0001.txt / corpus-go-vulndb-osv/go-2023-1737.txt / corpus-go-vulndb-osv/go-2021-0052.txt / corpus-go-vulndb-osv/go-2021-0063.txt / corpus-go-vulndb-osv/go-2026-5017.txt
grade: pass
Q: Why did Go 1.19.6 patch the x/net HTTP/2 code: what resource does GO-2023-1571 burn?
expect: corpus-go-vulndb-osv/go-2023-1571.txt
top-5: corpus-go-vulndb-osv/go-2023-1571.txt / corpus-go-vulndb-osv/go-2023-2102.txt / corpus-go-vulndb-osv/go-2026-4918.txt / corpus-go-vulndb-osv/go-2022-1144.txt / corpus-go-vulndb-osv/go-2023-1569.txt
grade: pass
Q: What hang did google.golang.org/protobuf fix in 1.33.0 per GO-2024-2611?
expect: corpus-go-vulndb-osv/go-2024-2611.txt
top-5: corpus-go-vulndb-osv/go-2024-2611.txt / corpus-go-vulndb-osv/go-2023-1631.txt / corpus-go-vulndb-osv/go-2021-0053.txt / corpus-go-vulndb-osv/go-2024-2978.txt / corpus-go-vulndb-osv/go-2024-3162.txt
grade: pass
Q: What input makes Go's TLS stack crash before the 1.16.6 fix?
expect: corpus-go-vulndb-osv/go-2021-0243.txt
top-5: corpus-go-vulndb-osv/go-2021-0243.txt / corpus-go-vulndb-osv/go-2022-1167.txt / corpus-go-vulndb-osv/go-2025-3966.txt / corpus-go-vulndb-osv/go-2026-5781.txt / corpus-go-vulndb-osv/go-2023-2375.txt
grade: pass
Q: What kind of message remotely crashes an unauthenticated Go SSH endpoint when AEAD ciphers are in use?
expect: corpus-go-vulndb-osv/go-2022-0968.txt
top-5: corpus-go-vulndb-osv/go-2024-2527.txt / corpus-go-vulndb-osv/go-2021-0356.txt / corpus-go-vulndb-osv/go-2026-5596.txt / corpus-go-vulndb-osv/go-2025-4135.txt / corpus-go-vulndb-osv/go-2026-6103.txt
grade: miss

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.