npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

markstone

v0.1.0

Published

Fast, safe Markdown-to-HTML and AST engine with Actos extensions for Node.js and the browser

Readme

markstone

Unified Node.js and browser package for markstone: fast, safe Markdown-to-HTML and AST engine with Actos extensions.

Uses native napi-rs addon on Node.js and WebAssembly (wasm-bindgen) in browsers via conditional exports. Both paths produce byte-for-byte identical output.

Installation

npm install markstone

Prebuilt addons ship for Linux (x64 and arm64, glibc 2.28+ and musl), macOS (x64 and arm64) and Windows (x64 and arm64). On any other platform, Node falls back to the WebAssembly build with no extra setup.

Usage

Node.js (Native Addon)

import markstone, { toHtml, toAst, actos } from 'markstone';

// Generic CommonMark + GFM
const html = toHtml('# Hello world');
const ast = toAst('# Hello world');

// Actos extensions (@mentions and #tags)
const actosHtml = actos.toHtml('Hello @alice and #rust');
const actosAst = actos.toAst('Hello @alice and #rust');

Browser (WebAssembly)

import markstone, { init, toHtml, toAst, actos } from 'markstone';

// Initialize WASM binary once in browser
await init();

// Render
const html = toHtml('# Hello from the browser');
const actosHtml = actos.toHtml('Hello @alice and #rust');

Security & Conformance

  • No raw HTML or dangerous scripts pass through the AST sanitizer.
  • Depth limit: 64 block levels (DEPTH_EXCEEDED).
  • Input limit: 4 MiB (INPUT_TOO_LARGE).
  • 100% byte-for-byte conformance parity between Node native and browser WASM.