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

remark-lint-visimark

v0.2.0

Published

A unified/remark plugin that runs visimark check over a document and reports findings as VFile messages.

Downloads

645

Readme

remark-lint-visimark

A unified/remark plugin that runs visimark check over a document already in your remark/remark-lint pipeline and reports its findings as VFile messages — the same channel remark-lint rules already use.

Install

npm i -D remark-lint-visimark
# or
bun add -d remark-lint-visimark

Use

.remarkrc.json:

{ "plugins": ["remark-preset-lint-recommended", "remark-lint-visimark"] }

or programmatically:

import { unified } from "unified";
import remarkParse from "remark-parse";
import remarkStringify from "remark-stringify";
import remarkLintVisimark from "remark-lint-visimark";

const file = await unified()
  .use(remarkParse)
  .use(remarkStringify)
  .use(remarkLintVisimark)
  .process(vfile);

(remark-stringify is only there because unified().process() requires a compiler to be registered; this plugin never uses the compiled output. A pipeline already built on the remark package, or on remark-cli, already has a compiler and needs no change.)

Every VisiMark finding with a source location becomes a file.message() call: fatal: true for a stale number or any other check-failing finding, fatal left unset (a warning, visible under remark --frail) for advice. ruleId is per finding kind (visimark-stale, visimark-assert, …), source is "visimark".

This plugin takes no options and performs no autofix — see docs/ci.md in the main repository for the full write-up.