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

nepali-profanity-checker

v1.0.3

Published

Nepali profanity detection and censoring (Devanagari + romanized variants).

Downloads

8

Readme

Nepali Profanity Checker

Lightweight Nepali profanity detection and censoring library (Devanagari + romanized variants).

Quick start

Build the library and run tests:

npm ci
npm run build
npm test

Run interactive console to try phrases manually:

npm run console

API

Import the library and use the helpers:

const { containsProfanity, findProfanities, censorProfanity } = require('./dist/index.js');

console.log(containsProfanity('तँ हरामी हो')); // true
console.log(findProfanities('तँ हरामी हो')); // details about matches
console.log(censorProfanity('तँ हरामी हो')); // 'तँ ***** हो'

// Fuzzy (approximate) matching example
console.log(containsProfanity('you are h4rami', { fuzzy: true }));

Features

  • Loads a curated JSON wordlist (src/data/badword.json) with variants and categories.
  • Unicode normalization (NFKC) and diacritic removal for robust matching.
  • Optional fuzzy matching (Levenshtein) to catch obfuscated/typo variants.
  • Simple censoring that preserves Unicode codepoint lengths.

Publishing

Before publishing run:

npm run build
npm pack  # creates a tarball to inspect what will be published
# then when ready:
npm publish

Contributing

Add/modify words in src/data/badword.json. Add unit tests under test/ and submit a PR. If you would like to add some profane words, please make sure it is unique than the Current List down below to avoid duplication. Please make sure to follow the json schema exactly [shown below] while making json data.

Current Profane Words List

[
  'harami',        'murkha',     'badmas',       'saley',
  'sali',          'kukur',      'randi',        'rande',
  'bhate',         'bhalu',      'machikni',     'chhakka',
  'lado',          'lauro',      'muji',         'puti',
  'chhuchi',       'chhura',     'turi',         'geda',
  'gu',            'gukhane',    'pakhe',        'boka',
  'bokni',         'jantha',     'condo',        'chaak',
  'chaak ko pwal', 'bhosdika',   'madarchod',    'bhenchod',
  'lund',          'lodo',       'chod',         'chodna',
  'rakhnu',        'pesa',       'gand',         'gandako',
  'gandu',         'pesa garne', 'sungur',       'budi',
  'budo',          'chikney',    'lundra',       'lundri',
  'gadha',         'kutta',      'kichkich',     'thukk',
  'nalayak',       'beijjat',    'ghrina',       'ninda',
  'kachara',       'nikamma',    'sasto manche', 'gali',
  'fohor',         'ghinlagdo',  'nindaniya',    'gand',
  'gandako',       'gandu',      'chutiya',      'bekar',
  'jhola',         'chor',       'hijada',       'pagal',
  'kutne',         'latti',      'beshya',       'bokshi',
  'chaak',         'Chickne',    'Gula',         'moot',
  'murda',         'bajiya', 'khate', 'torpe',
  'daka',  'paji',
  'dhoti', 'radi',
  'paad',  'mukhulla',
  'gobre', 'bhusya',
  'dhurt', 'bhaisi, 'kamina', 'kutti', 'haramzada'
]

Json Data Format

Each profane word must follow the structure below.

{
  "base": "kutti", # Data type is string. The canonical form of the profane word written in Roman script.
  "nepali": ["कुत्ती"], #  Data type is string. The word written in Devanagari (Nepali/Hindi script).
  "variants": [
    "kutti",
    "kuttiii",
    "kutt1",
    "k@tti"
  ], # Data type for variants is string[]. Common alternative spellings, misspellings, or obfuscated forms used to bypass profanity filters.
  "category": ["sexual", "insult"] # Data type for category is string[]. Labels describing the type of profanity. Used for filtering and severity control.
}

License

MIT License

Copyright (c) 2025 Subin Bista

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.