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

@marro-sh/core

v0.2.0

Published

The Marro contract: types, limits, path rules, content negotiation. Shared by the CLI and marro.sh.

Readme

@marro-sh/core

The shared contract behind marro.sh: the types, limits, path rules, reserved names, MIME map and content negotiation that both the @marro-sh/cli client and the marro server consume.

It exists so the two surfaces cannot drift. A refusal means the same thing in a terminal as it does over HTTP, because both read these rules.

npm install @marro-sh/core
import { CONTEXT_TYPES, FILE_LIMIT, isContextType, resolvePath } from "@marro-sh/core";

isContextType("notes.md");   // true
isContextType("clip.mp4");   // false
FILE_LIMIT;                  // 5 MB, in bytes

You probably want the CLI rather than this package. This one is published so the CLI can depend on a real version rather than a bundled copy.

Licence

MIT. See LICENSE.