Discofork
Repository brief

markedjs/marked

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T20:07:14.706Z
1mo ago

markedjs/marked

markedjs/marked is a popular markdown parser/compiler focused on speed. It is actively maintained, not archived, and ships a CLI, browser bundles, TypeScript types, docs, and tests. The repository looks mature and release-oriented, with recent security/performance fixes and a large fork/stars base, so forks are most interesting if you care about markdown parsing, CLI tooling, or performance/security hardening.

GitHub
Loading tags...
Stars36,732
Forks3,516
Default branchmaster
Last pushed2026-03-30T17:04:15Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you need its legacy React output model and are maintaining an existing integration. For new work, upstream marked is the safer default because this fork is heavily out of date and likely missing most modern fixes and packaging improvements.

Choose this fork only if its CJK-specific syntax is the product requirement. If you mainly want a fast, maintained Markdown parser, upstream Marked is the safer default.

Choose this fork only if you need its legacy color/highlight customization or component-style integration and can accept a frozen codebase. For most adopters, upstream Marked is the better choice because it is actively maintained, much more complete, and has current security and packaging support.

Choose upstream unless you specifically need this fork's legacy behavior or older integration quirks. This fork is a significant divergence point with stale maintenance and likely misses important upstream fixes and modern packaging.

Prefer this fork only if its validation/accessibility changes are specifically valuable to you and you are prepared to carry 99 commits of upstream drift. For most adopters, upstream marked is the safer default because it is much more current and actively maintained.

Choose this fork only if you need its legacy Chinese/localized syntax extensions or already depend on its output. For new work, upstream marked is the safer choice because this fork is stale and materially behind.

Prefer upstream marked unless you need this fork's historical API cleanup or pluggable-parser experiment. For new work, this fork is too stale and too divergent to be a safe default.

Choose this fork only if you need its older, more opinionated parser behavior and are prepared to maintain a stale codebase. If you want current marked features, fixes, and support, upstream is the better default.

Choose this fork if you need Mattermost-specific markdown behavior, especially URL filtering and custom rendering. Choose upstream if you want the broadest compatibility, fastest access to fixes, and the least maintenance burden.

Prefer upstream unless you explicitly need this older snapshot or its local doc/demo/test tweaks. For most adopters, the fork is too stale and too far behind to justify using over current Marked.

markedjs/marked · Discofork