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

rdktr

v0.1.3

Published

Fast stop-word / text-cleanliness checker

Downloads

39

Readme

rdktr

Fast stop-word / text-cleanliness checker ("Glavred"-style) for Russian and English. A WebAssembly build of a C core — zero dependencies, less then 400 KB wasm (rules included), works in browsers and Node.

The language is detected automatically per paragraph (Cyrillic vs Latin script with a document-level fallback), so mixed-language documents get Russian hints for Russian paragraphs and English hints for English ones.

Usage

import { createChecker } from "rdktr";

const checker = await createChecker();
const text = "Данный подход работает.\n\nThis is a very good approach.";

for (const issue of checker.check(text)) {
    // offsets are plain JS string indices (UTF-16 code units)
    console.log(
        text.slice(issue.start, issue.end), // "Данный", "very"
        issue.rule.title,                   // "Канцеляризм", "Intensifier"
        issue.rule.hint,                    // advice in the paragraph's language
        issue.rule.language,                // "ru", "en"
        issue.rule.weight,
    );
}

checker.destroy(); // frees wasm-side memory

createChecker() loads rdktr.wasm shipped with the package. Pass a URL, ArrayBuffer or precompiled WebAssembly.Module to load it from somewhere else (e.g. a CDN or a bundler asset).

Building from source

The wasm module is prebuilt. To rebuild it from the C core you need zig (bundles clang + lld + wasi-libc):

npm run build
npm run test

Rules are Markdown files compiled ahead of time; see the monorepo root for the rule format and the offline compiler.