big-list-of-naughty-strings VS eslint-plugin-no-unsanitized

Compare big-list-of-naughty-strings vs eslint-plugin-no-unsanitized and see what are their differences.

big-list-of-naughty-strings

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. (by minimaxir)

eslint-plugin-no-unsanitized

Custom ESLint rule to disallows unsafe innerHTML, outerHTML, insertAdjacentHTML and alike (by mozilla)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
big-list-of-naughty-strings eslint-plugin-no-unsanitized
41 2
45,851 215
- 1.9%
0.0 4.6
10 days ago 5 days ago
Python JavaScript
MIT License Mozilla Public License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

big-list-of-naughty-strings

Posts with mentions or reviews of big-list-of-naughty-strings. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-20.

eslint-plugin-no-unsanitized

Posts with mentions or reviews of eslint-plugin-no-unsanitized. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-17.
  • Escaping user input is ridonkulously hard
    2 projects | /r/programming | 17 Oct 2022
    Prevent any uses of setting innerHTML or similar functions e.g. via an eslint plugin.
  • HTML Sanitizer API
    5 projects | news.ycombinator.com | 6 May 2021
    Great point!

    It wanted to edit the comment to change (1) to (server/client) but I passed my edit timeout.

    I would include your (5) within (1). `textContent` and other DOM methods like `setAttribute` are effectively secure output-escaping on the client.

    Your (5a) is an excellent extra measure. In this area, I'd also add security-focused linting for (1) and (5)–e.g. for (5), to ensure secure DOM methods are used, I use Mozilla's `eslint-plugin-no-unsanitized`[0] plugin for all my personal & work projects.

    [0] https://github.com/mozilla/eslint-plugin-no-unsanitized/

What are some alternatives?

When comparing big-list-of-naughty-strings and eslint-plugin-no-unsanitized you can also consider the following projects:

SecLists - SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place. List types include usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells, and many more.

java-html-sanitizer - Takes third-party HTML and produces HTML that is safe to embed in your web application. Fast and easy to configure.

CheatSheetSeries - The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific application security topics.

content - The content behind MDN Web Docs

ms-teams-rce

You-Dont-Need-Lodash-Underscore - List of JavaScript methods which you can use natively + ESLint Plugin

javascript-questions - A long list of (advanced) JavaScript questions, and their explanations :sparkles:

XO - ❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults

bluemonday - bluemonday: a fast golang HTML sanitizer (inspired by the OWASP Java HTML Sanitizer) to scrub user generated content of XSS

33-js-concepts - 📜 33 JavaScript concepts every developer should know.

WSL - Issues found on WSL