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

slop-chop-wasm

v0.42.1

Published

Chop AI slop from text. The slop-chop rules engine as WebAssembly, no network, no model.

Readme

slop-chop-wasm

Chop AI slop from text, in-process. This is the slop-chop rules engine compiled to WebAssembly, wrapped for Node. No network, no model, no data leaves the machine, and the same input always gives the same output.

Use

const slop = require("slop-chop-wasm");

const res = await slop.chop("In summary, we leverage a myriad of robust tools.");
res.output;           // "We use many solid tools."
res.score.value;      // 80, the input
res.scoreAfter.value; // 0, the output
res.findings;         // every tell, with rule, match, and offsets

Rate without rewriting:

await slop.score("Needless to say, synergy abounds."); // 0 to 100

Options

await slop.chop(text, {
  presets: ["cleaver"],                    // built-in preset names; cleaver is the default
  voice: {                                  // your voice, folded on top
    keep: ["gnarly"],                       // never flag or cut these
    prefer: { utilize: "use" },             // your swap wins
    avoid: ["synergy"],                     // flag these wherever they appear
  },
  profile: undefined,                       // full profile override; defaults to the built-in
});

defaultProfile() returns the built-in profile to tweak, presetNames() lists the packs, and version() reports the engine build. init() front-loads the wasm startup, otherwise the first call pays it.

Build from source

The engine ships in the package under engine/. In the repo, make npm-package builds and stages it.

MIT. From slop-chop.