Hysen Labs
Open-source project
minimaxir/big-list-of-naughty-strings avatar
minimaxir

big-list-of-naughty-strings

GitHub describes it as The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.. The repository metadata lists Python as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

47,706 stars2,154 forksPythonMIT
01
DEEP OPEN-SOURCE ANALYSIS

minimaxir/big-list-of-naughty-strings: Big List of Naughty Strings

GitHub describes it as The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.. The repository metadata lists Python as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

02
DEEP OPEN-SOURCE ANALYSIS

Repository scope

GitHub describes it as The Big List of Naughty Strings is a list of strings which have a high probability of causing issues when used as user-input data.. The repository metadata lists Python as its primary language. The metadata lists the MIT license. The README describes the project this way: The Big List of Naughty Strings is an evolving list of strings which have a high probability of causing issues when used as user-input data. This is intended for use in helping both automated and manual QA testing; useful for whenever your QA engineer walks into a bar.

03
DEEP OPEN-SOURCE ANALYSIS

Why Test Naughty Strings?

The README section "Why Test Naughty Strings?" states: Even multi-billion dollar companies with huge amounts of automated testing can't find every bad input. For example, look at what happens when you try to Tweet a zero-width space (U+200B) on Twitter:

04
DEEP OPEN-SOURCE ANALYSIS

Why Test Naughty Strings?

The README section "Why Test Naughty Strings?" states: Although this is not a malicious error, and typical users aren't Tweeting weird unicode, an "internal server error" for unexpected input is never a positive experience for the user, and may in fact be a symptom of deeper string-validation issues. The Big List of Naughty Strings is intended to help reveal such issues.

05
DEEP OPEN-SOURCE ANALYSIS

Usage

The README section "Usage" states: blns.txt consists of newline-delimited strings and comments which are preceded with . The comments divide the strings into sections for easy manual reading and copy/pasting into input forms. For those who want to access the strings programmatically, a blns.json file is provided containing an array with all the comments stripped out (the scripts folder contains a Python script used to generate the blns.json ).

06
DEEP OPEN-SOURCE ANALYSIS

Editorial conclusion

The repository README is the source for this review. It does not replace a local installation or an independent test.

07
DEEP OPEN-SOURCE ANALYSIS

Official sources

08
Community notes

Community notes