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

flood-detector

v1.0.5

Published

Provides a function which evaluates if a text looks like flood or normal text using lz algorithm

Downloads

8

Readme

flood-detector

Javascript detection of repetitive strings using the LZ algorithm

How it works ?

When people type garbage messages in order to be annoying, they tend to repeat word or letters or to use specific patterns which will allow a better compression of the string. By LZ-compressing the string and looking how much we were able to reduce its size, we can estimate if the text is garbage or real text.

This is not perfect and I think maybe there is a better solution for this. Don't hesitate to tell me if you know a better way.

This is currently active on https://fr.lou.lt/ to avoid annoying floods. Short demo can be found here.

Node.js

npm install flood-detector

then:

FloodDetector = require('flood-detector');
if (FloodDetector.evaluate(string)) {
  console.log('probably not flood');
} else {
  console.log('probably flood');
}

There is an optional parameter to change the trigger value (default value is 30) :

// This will return true only if the compressed string has more than 40% of the size of the original string
FloodDetector.evaluate(string, 40); 

Bower

bower install flood-detector

then:

<script src="bower_components/lz-string/libs/lz-string.min.js"></script>
<script src="bower_components/flood-detector/flood-detector.js"></script>
<script>
  if (FloodDetector.evaluate(string)) {
    console.log('probably not flood');
  } else {
    console.log('probably flood');
  }
</script>

Yeah, that's a damn small package but very useful for me.

License

DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE 
                  Version 2, December 2004 

Copyright (C) 2004 Sam Hocevar <[email protected]> 

Everyone is permitted to copy and distribute verbatim or modified 
copies of this license document, and changing it is allowed as long 
as the name is changed. 

          DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE 
 TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 

0. You just DO WHAT THE FUCK YOU WANT TO.