yuin/goldmark

:trophy: The Golden Swiss Army Knife for markdown processing. 100% CommonMark compliant, AST w/ CST, Extensible, Fast, CJK-friendly.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 13th, 2026
Created on April 26th, 2019
Open Issues & Pull Requests: 23 (+0)
GitHub issues: Enabled
Number of forks: 316
Total Stargazers: 5,027 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.5 hours
Mean response time: 8.9 days
90th percentile: 30.4 days
Tracked items: 54

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 19
Closed in 7 days: 19
Avg open age: 648 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 19
Closed in 7 days: 19
Comments in 7 days: 0
Events in 7 days: 19

Top labels

  • stale (8)
  • v1 (5)
  • pinned (4)
  • v2 (3)

Detailed Description

goldmark is a Markdown parser written in Go that prioritizes extensibility, performance, and standards compliance with CommonMark.

The tool solves the problem of parsing Markdown documents into structured formats while maintaining ease of extension. It uses a well-structured architecture that separates concerns between parsing and rendering, allowing developers to add custom syntax and generate output in multiple formats beyond HTML. The parser builds an abstract syntax tree that can be analyzed semantically or used to construct Markdown documents programmatically.

Developers should choose goldmark if they need a performant, standards-compliant Markdown parser in Go with the ability to extend it for custom syntax. It suits projects ranging from static site generators to language server implementations and AI-driven document analysis tools. The project explicitly acknowledges that use cases have evolved significantly since its initial creation, particularly around semantic analysis of Markdown documents and generation rather than just parsing.

The project maintains a clear separation between major versions, with bug fixes provided for one version prior to the latest release. Development has undergone a substantial architectural review to address technical debt accumulated over years of use, introducing breaking changes in the current major version to support generics, improved semantic AST construction, and clearer parser-renderer separation. The maintainer has provided migration tooling and documentation to help users transition from earlier versions, recognizing the impact of breaking changes on third-party extensions within the ecosystem.