Benchmark: sanitize-html vs nothing

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/sanitize-html/1.27.5/sanitize-html.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/dompurify/2.2.7/purify.min.js"></script>

Tests:

DOMPurify
const testString = `aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa` const result = testString console.log(result)
Sanitize HTML
const testString = ` <b>Welcome to safeland</b><br> <a href='javascript:alert(1)'>This is fun</a><br> <img src=x onerror=console.log(1)> ` const result = sanitizeHtml(testString) console.log(result)

Historical Performance Data aggregated from 9 community runs

Desktop Results:

Chrome 9 runs

DOMPurify

164K/s

Sanitize HTML

22K/s

Fastest: DOMPurify (7.6x faster)

View exact numbers

✓ DOMPurify: 164,021 ops/sec
• Sanitize HTML: 21,638 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
DOMPurify
Sanitize HTML

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36

Browser/OS: Chrome 135 on Windows

View result in a separate tab

DOMPurify

238K/s

Sanitize HTML

32K/s

View exact numbers

Test name	Executions per second
✓ DOMPurify	237,769 Ops/sec
Sanitize HTML	31,575 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

Let's break down the provided benchmark definitions and options.

**Options being compared:**

In the first test case, `DOMPurify` is being tested against a "Nothing" approach (no sanitization). The two approaches being compared are:

1. **DOMPurify**: A library that removes or escapes HTML tags from input strings to prevent XSS attacks.
2. **Nothing**: No sanitization is applied, which means the input string is not modified.

Pros of using `DOMPurify`:

* Provides robust protection against XSS attacks
* Easy to use and configure

Cons of using `DOMPurify`:

* May introduce unnecessary overhead or performance penalties
* Can be slower than no sanitization for simple cases

Pros of "Nothing" approach:

* No additional overhead or performance penalties
* Faster execution times for simple cases

Cons of the "Nothing" approach:

* Leaves input strings vulnerable to XSS attacks

**Second test case:**

In this test case, `Sanitize HTML` is being compared against no sanitization. The two approaches being compared are:

1. **Sanitize HTML**: A library that removes or escapes HTML tags from input strings while preserving some syntax and structure.
2. **Nothing**: No sanitization is applied.

Pros of using `Sanitize HTML`:

* Preserves some original syntax and structure while removing malicious code
* May be faster than `DOMPurify` for certain cases

Cons of using `Sanitize HTML`:

* May not remove all possible XSS attacks
* Can be slower than no sanitization for extremely simple cases

Pros of the "Nothing" approach:

* Faster execution times for extremely simple cases
* No overhead or performance penalties

Cons of the "Nothing" approach:

* Leaves input strings vulnerable to XSS attacks

**Library and syntax explanations:**

1. `sanitize-html` is a library developed by Dave Shaw (a.k.a. "dfshaw") that provides a fast and efficient way to sanitize HTML input.
2. `dompurify` is another popular library for sanitizing HTML input, developed by Paul Miller.
3. In the first test case, the `testString` variable contains an XSS attempt using a script tag. The expected output of both approaches is an empty string.
4. In the second test case, the `testString` variable contains multiple HTML elements (bold, link, and image) with malicious attributes. Both approaches are expected to remove or escape these malicious attributes.

**Other alternatives:**

* Other sanitization libraries include `html-minifier`, `js-xss-sanitizer`, and `xss-cleaner`.
* Some browsers have built-in XSS protection mechanisms, such as Google Chrome's Content Security Policy (CSP) feature.
* For extremely simple cases, no sanitization or a custom approach may be sufficient.

Overall, the choices between these approaches depend on the specific use case and requirements. If you need robust protection against XSS attacks, `DOMPurify` is a good choice. If you prioritize performance over security, "Nothing" might be acceptable for very simple cases.

sanitize-html vs nothing (version: 0) Benchmark.js

Comparing performance of: `DOMPurify vs Sanitize HTML`

Created: 5 years ago by: Guest

Go to the latest result

DOMPurify

Sanitize HTML

Historical Performance Data aggregated from 9 community runs

Desktop Results:

Chrome 9 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

sanitize-html vs nothing (version: 0) Benchmark.js

Comparing performance of: DOMPurify vs Sanitize HTML

Created: 5 years ago by: Guest

Go to the latest result

DOMPurify

Sanitize HTML

Historical Performance Data aggregated from 9 community runs

Desktop Results:

Chrome 9 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `DOMPurify vs Sanitize HTML`