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 🙏

© 2024 – Pkg Stats / Ryan Hefner

phrase-blacklist

v2.0.0

Published

Filter out strings with banned words and bypasses some evasion

Downloads

37

Readme

phrase-blacklist

Filter out strings with banned words and bypasses some evasion

Installing

Using NPM

npm i phrase-blacklist  

THIS IS IN ALPHA. Please save version numbers in your package.json as I may be making many breaking changes in the future. Saving your package version will keep your package version the same, thus unaffected by major changes.

Example

Import

const phraseBlacklist = require('phrase-blacklist')

Check if text is clean

phraseBlacklist.isClean('fucc that hurts!!', <options object>) 
//Returns true if text is safe
//Returns a string, the detected bad word, if the text contains a banned phrase
options:
[note: each option runs default if not defined. will not trigger action if set false]

innerHTMLOnly : boolean //Strips HTML elements from the text //defaults to false

clearDuplicates : object //Removes duplicate characters from the text. Does a layered check using the converted text. //defaults to {fromEachWord: true}

translateMaskChars : boolean //Prevent filter evasion by translating characters to another (ex. @ = a) //defaults to true

Get potential original message from masked characters

phraseBlacklist.translateMaskChars('I n33d t0 $h1t!!') 
//Returns the potential original message

Clients may try to bypass a chat filter in place by using characters similar, yet different to the intential characters.

Remove repeat characters

phraseBlacklist.RemoveRepeatCharacters('heeeeeckkkkkkk youu!')
//Returns, 'heck you'

Strip HTML tags

 phraseBlacklist.ExtractInnerHTML('<p attribute="hello">world</p>')
 //Returns, 'world'

Add to blacklist

phraseBlacklist.BanPhrases('https://') 
//Adds 'https://' to the list of banned phrases
//isClean('https://website.com') would then return false
//The parameter can be a single string or an array of strings

Remove from blacklist

phraseBlacklist.UnbanPhrases('https://') 
//Removes 'https://' to the list of banned phrases (If so added)
//isClean('https://') would then return true
//The parameter can be a single string or an array of strings

Contributing

To contribute to phrase-blacklist you first should fork the repository on GitHub and clone it to your local machine.

After making your changes you should first run the existing test.js file and then add any new relevent tests if appropriate. If you are fixing a bug we recommend you create a test that tests your fix to prevent regressions in the future.