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

@binkylabs/muzzle

v1.2.2

Published

A muzzle for your TypeSpec linting rules. It's experimental, slightly unethical, and definitely effective.

Readme

TypeSpec Muzzle

Welcome to the TypeSpec Muzzle project. This project aims to provide tooling to suppress TypeSpec linting issues from the CLI. This is useful if you want to establish a baseline suppression in your TypeSpec definition without having to disable the rules entirely. For example when starting a new project from an OpenAPI import, or trying to enable new rules with existing infringements on an existing projects.

Usage

CLI

  1. Install the CLI with

    npm i -g @binkylabs/muzzle
  2. Ensure the ruleset or emitter you want to suppress is also installed

    # example you use the @typespec/http/recommended ruleset and the @azure-tools/typespec-autorest emitter
    npm i @typespec/http @azure-tools/typespec-autorest
  3. Suppress all warnings generated by the ruleset

    muzzle main.tsp --rule-set "@typespec/http/recommended" -m "auto-suppression"
    
    # Or for an emitter
    muzzle main.tsp --emiter "@azure-tools/typespec-autorest"

API

  1. Install the package with

    npm i -S @binkylabs/muzzle
  2. Ensure the ruleset you want to suppress is also installed

    # example you use the @typespec/http/recommended ruleset and the @azure-tools/typespec-autorest
    npm i -S @typespec/http @azure-tools/typespec-autorest
  3. Use the suppression method

    import { parseTypeSpecAndSuppressEverything } from "@binkylabs/muzzle";
    
    await parseTypeSpecAndSuppressEverything(
       {
          entryPoint: "path/to/main.tsp", 
          ruleSets: ["@typespec/http/recommended"],
          emitters: ["@azure-tools/typespec-autorest"],
          message: "auto-suppression"
       }
    );

Debugging

  1. Install dependencies with

    npm i
  2. Build the library with

    npm run build
  3. Run unit tests with

    npm run test