markedjs/marked

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.