naughty-words

v1.2.0

An npm package to use the List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words For more information about how to use this package see README

Latest version published 4 years ago

License: CC-BY-4.0

NPM

GitHub

Package Health Score

57 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Sustainable

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
1.2.0	\|	07/2020	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.0	\|	01/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.2	\|	07/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

CC-BY-4.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (3,653)

GitHub Stars: 2.93K
Forks: 663
Contributors: 60

Direct Usage Popularity

The npm package naughty-words receives a total of 3,653 downloads a week. As such, we scored naughty-words popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package naughty-words, we found that it has been starred 2,930 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 60
Funding: No

With more than 10 contributors for the naughty-words repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like naughty-words is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 30
Open PR: 72
Last Release: 4 years ago
Last Commit: 4 years ago

Further analysis of the maintenance status of naughty-words based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for naughty-words is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 8 years
Dependencies: 0 Direct
Versions: 6
Install Size: 68.7 kB
Dist-tags: 1
# of Files: 38
Maintainers: 4
TS Typings: No

naughty-words has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Our List of Dirty, Naughty, Obscene, and Otherwise Bad Words

With millions of images in our library and billions of user-submitted keywords, we work hard at Shutterstock to make sure that bad words don't show up in places they shouldn't. This repo contains a list of words that we use to filter results from our autocomplete server and recommendation engine.

Please add to it as you see fit (particularly in non-English languages) or use it to spice up your next game of Scrabble 😃

Obvious warning: These lists contain material that many will find offensive. (But that's the point!)

Miscellaneous caveat: Clearly, what goes in these lists is subjective. In our case, the question we use is, "What wouldn't we want to suggest that people look at?" This of course varies between culture, language, and geographies, so in the end we just have to make our best guess.

Languages

Name	Code
Arabic	ar
Chinese	zh
Czech	cs
Danish	da
Dutch	nl
English	en
Esperanto	eo
Filipino	fil
Finnish	fi
French	fr
French (CA)	fr-CA-u-sd-caqc
German	de
Hindi	hi
Hungarian	hu
Italian	it
Japanese	ja
Kabyle	kab
Klingon	tlh
Korean	ko
Norwegian	no
Persian	fa
Polish	pl
Portuguese	pt
Russian	ru
Spanish	es
Swedish	sv
Thai	th
Turkish	tr

Install

You can add the list to your client side project using Bower.

$ bower install --save naughty-words

You can add the list to your Javascript project using NPM.

$ npm install --save naughty-words

Usage

Browser

In the browser you can use the json files directly with a get request:

Node

You can require the json file directly.

var deutsche = require("naughty-words/de.json");
console.log(deutsche);

You can browse the languages by requiring the whole module.

var words = require("naughty-words");
console.log(words);
console.log(words.de);

See also the list of projects, documents, and organizations that use these lists.

This work is licensed under a Creative Commons Attribution 4.0 International License.

FAQs

What is naughty-words?

An npm package to use the List-of-Dirty-Naughty-Obscene-and-Otherwise-Bad-Words. Visit Snyk Advisor to see a full health score report for naughty-words, including popularity, security, maintenance & community analysis.

Is naughty-words popular?

The npm package naughty-words receives a total of 3,653 weekly downloads. As such, naughty-words popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is naughty-words well maintained?

We found indications that naughty-words is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is naughty-words safe to use?

The npm package naughty-words was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 11 November-2024, at 10:01 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP