Install marked with Homebrew

Project links

• Homepage

Commands and aliases

• marked

Project history

Marked began in 2011 under Christopher Jeffrey and later moved into the markedjs organization. The official license file preserves that history by distinguishing the 2011-2018 copyright period from the MarkedJS-maintained period that followed.

The GitHub repository and npm package were both created on 2011-07-24, putting Marked among the older Markdown packages in the Node.js package ecosystem. Its documentation emphasizes speed, browser/server/CLI use, and an extension model through marked.use().

Adoption history

Marked became a widely packaged Markdown implementation: by 2026-07-01 the GitHub repository reported 36,943 stars and 3,551 forks, while the npm package metadata showed version 18.0.5 as the current release. The supplied package-manager facts also list Homebrew, Fedora, and Arch packages, showing distribution beyond npm.

The project remained active through frequent 2026 releases, with GitHub release notes for v18.0.x documenting parser and CLI fixes. That maintenance cadence matters because Markdown parsers live in a long tail of edge cases, security expectations, and compatibility questions.

How it is used

Marked is used both as a library and as a command-line program. The README shows CLI conversion with marked -o and JavaScript usage through marked.parse(), while the official docs warn that Marked does not sanitize generated HTML and should be paired with a sanitizer when rendering untrusted content.

For package maintainers, Marked is the sort of dependency that sits underneath documentation sites, static-site tools, server renderers, browser previews, and conversion scripts. Its package metadata exposes a marked binary and ESM/browser entry points, matching the multi-runtime story in the official docs.

Why package nerds care

Marked is historically important because it is both an npm-era Markdown parser and a CLI in one package. Its long version history, large downstream use, and explicit no-sanitization boundary make it a useful case study in how small parsing packages become infrastructure.

Timeline

• 2011: GitHub repository and npm package created.
• 2018: Maintenance identity reflected as MarkedJS in the project license.
• 2026: v18.0.5 published and repository metadata showed more than 36,000 stars.

Related projects

• Marked is commonly compared with markdown-it, CommonMark reference implementations, and markdown-it-based tooling.
• marked-highlight and marked-man appear in the package ecosystem around syntax highlighting and man-page generation.

Sources

• https://github.com/markedjs/marked
• https://marked.js.org/
• https://raw.githubusercontent.com/markedjs/marked/master/README.md
• https://registry.npmjs.org/marked