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

@master/internal-skills

v0.1.9

Published

First-party Master site, design and editorial skills with explicit synchronization

Readme

@master/internal-skills

Publicly distributed for first-party Master repositories. This is an internal contract, pinned to an exact version by each consumer.

Create .agents/master-skills.json with { "skills": ["master-site", "master-design", "master-writing"] }, then run master-skills sync. Commit .agents/skills/ and .agents/skills/.master-lock.json. CI runs master-skills check.

Synchronization is explicit. Installation never writes to a repository or global skill directory. Locally modified managed files and conflicting unmanaged files stop synchronization before any writes. Product skills outside the selected managed files are preserved. Edit shared skills in the Master repository; keep product extensions in their own skill directories.

Publishing

Master's publish.yml workflow validates the site and packages, retains the packed archives, then publishes those exact bytes through npm Trusted Publishing. The trusted publisher is GitHub repository master-co/master, workflow publish.yml, with no GitHub environment. Versions are committed before dispatch; consumers upgrade exact pins after registry integrity verification. No npm token is stored in GitHub. Master remains private, so these releases use OIDC without public provenance attestations.

Design source

Master Design is generated from the canonical portable skill in master-co/design. design-source.json pins the complete content snapshot and per-file hashes. In the Master checkout, explicitly run bun run design:sync /path/to/reviewed/skills/master-design, then bun run design:check. Review and commit that snapshot before publishing; consumers use the existing explicit skill sync. Installation never fetches a branch or modifies global skills. Edit site and writing skills here, and design guidance in its source repository.