remarkjs/remark

markdown processor powered by plugins part of the @unifiedjs collective

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 28th, 2014
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 384
Total Stargazers: 8,997 (+0)
Total Subscribers: 61 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.7 hours
Mean response time: 4.3 hours
90th percentile: 21.0 hours
Tracked items: 16

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 124 days
Stale 30+ days: 2
Stale 90+ days: 1

Recent activity

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

Top labels

  • 👎 phase/no (9)
  • 🤞 phase/open (4)
  • 👀 no/external (3)
  • 💪 phase/solved (3)
  • 🙅 no/wontfix (3)
  • 📚 area/docs (2)
  • 🙋 no/question (2)
  • 🤷 no/invalid (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

remark is a markdown processor powered by plugins that is part of the unified collective.

remark solves the problem of transforming and inspecting markdown by representing it as abstract syntax trees (ASTs). This approach allows plugins to examine and modify markdown content at a structural level rather than treating it as plain text. The tool works by parsing markdown into an AST representation called mdast, allowing plugins to operate on this structured data, then optionally converting the modified tree back to markdown or other formats. The ecosystem includes over 150 plugins that can be combined to achieve different outcomes, from adding support for GitHub Flavored Markdown and MDX to linting and formatting markdown files.

Developers should choose remark when they need to programmatically inspect or transform markdown content. It suits projects that require markdown processing on the server, client, CLIs, or Deno environments. The tool is compliant with CommonMark and can support GFM or MDX through plugins. If your goal is simply converting markdown to HTML with a few extensions, the README recommends micromark as a lighter alternative. remark is particularly valuable when you need to build custom markdown workflows or apply multiple transformations through its plugin system.

The project maintains a monorepo structure containing remark-parse for converting markdown to ASTs, remark-stringify for converting ASTs back to markdown, the core remark package combining both, and remark-cli for command-line usage. Development activity shows consistent engagement with the ecosystem, with the project serving as a foundational component within the unified collective alongside mdast and other related tools.