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

@maptiles-doctor/report

v0.1.1

Published

Static HTML and SARIF renderers for MapTiles Doctor reports.

Readme

@maptiles-doctor/report

Renderers that turn a MapTiles Doctor report into something a human or a tool can read. Rendering is kept out of the check engine, so @maptiles-doctor/core never has to know how a report is displayed.

📖 Documentation

Install

npm install @maptiles-doctor/report

Requires Node 24.18.1 or newer.

Usage

import { writeFile } from "node:fs/promises";
import { checkStyleContract } from "@maptiles-doctor/core";
import { renderHtmlReport, renderSarif } from "@maptiles-doctor/report";

const report = await checkStyleContract({ stylePath: "style.json" });

await writeFile("report.html", renderHtmlReport(report));
await writeFile("results.sarif", renderSarif(report));

API

| Function | Returns | | -------------------------- | -------------------------------------------------------------------------------------------------------------------- | | renderHtmlReport(report) | A standalone HTML page — no external assets, no build step. The VS Code extension shows this beside the editor. | | renderSarif(report) | SARIF 2.1.0, for GitHub code scanning and any other SARIF consumer. Severities map to error, warning and note. |

Both take a DoctorReport from @maptiles-doctor/core and return a string.

License

Apache-2.0