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

marxml

v0.1.2

Published

Fast markdown + XML query and mutation. Rust core with native Node bindings.

Readme

[!WARNING] Pre-1.0 · under active development. marxml is on 0.X.X and APIs, types, and selector grammar may still shift between minor versions. Not recommended for production yet — pin a specific version and read the changelog before bumping. Licensed MIT/Apache-2.0 (so it's always at your own risk anyway).

marxml lets you read and write XML-shaped tags embedded in markdown documents. Find them with CSS-style selectors, change them surgically, validate they're well-formed — without rewriting the prose around them. Native speed in Node via prebuilt binaries.

Features

  • Find tags with selectors. task[id^="4."], phase > task, note:not([archived]) — the CSS subset you already know.
  • Edit surgically. Change an attribute or replace inner content. Every byte you didn't touch comes back identical: prose, whitespace, comments, ordering.
  • Validate the shape. Required attributes, enum/regex constraints, child rules — declarative schema, structured errors with line numbers.
  • Native speed. Prebuilt .node binaries for macOS (arm64, x64) and Linux (x64-gnu, x64-musl, arm64-gnu). No build step. Windows support is pending — track the repo.

Why?

marxml started as plumbing for a workflow agent — plan and phase-planning documents (think GSD-style trackers) stored as markdown with task state inside XML tags. Agents needed to update those tags reliably: flip a status, append a note, mark a child done — without rewriting the surrounding prose or hallucinating new structure.

The general lesson: LLMs drift at the prose level but stay disciplined inside known XML tags. Scope the model's output to a tag, and the read/write boundary becomes deterministic again. marxml is the read/write layer for that boundary — selectors to find tags, byte-preserving mutation to change them, schema to verify what came back.

Install

pnpm add marxml
# or: npm install marxml
# or: yarn add marxml
# or: bun add marxml

Node >= 18. The right platform binary is pulled in as an optional dependency.

Quickstart

import { parse } from 'marxml'

const src = `
<phase id="1" status="todo">
  <task id="1.1" status="todo">do this</task>
  <task id="1.2" status="done">finished</task>
</phase>
`

const doc = parse(src)

for (const task of doc.select('task[status="todo"]')) {
  console.log(task.attrs.id) // "1.1"
}

const updated = doc.updateAttrs('task[status="todo"]', [
  { name: 'status', value: 'done' },
])

Docs

Full documentation lives in the repository:

  • Node referenceMarkdownDoc shape, distribution, regex behavior.
  • DSL reference — selectors, validation schema, cookbook recipes, formal grammar.
  • Architecture — tokenizer, mutation strategy, two-track API.

There's also a Rust crate of the same name — same API surface, shared source of truth.

License

Dual-licensed under either MIT or Apache 2.0 at your option.