Convert Figma logo to code with AI

rgrove logosanitize

Ruby HTML and CSS sanitizer.

2,021
139
2,021
1
View on GitHubView on NPM

Top Related Projects

gjtorikian's avatar

html-pipeline

2,266

HTML processing filters and utilities

cure53's avatar

DOMPurify

13,621

DOMPurify - a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMPurify works with a secure default, but offers a lot of configurability and hooks. Demo:

Quick Overview

Sanitize is a Ruby library for HTML sanitization. It provides a flexible and powerful way to clean up user-generated HTML content, removing potentially malicious or unwanted elements and attributes while preserving safe content.

Pros

  • Highly customizable with configurable elements, attributes, and protocols
  • Supports both allowlist and denylist approaches for fine-grained control
  • Actively maintained and compatible with modern Ruby versions
  • Extensive test suite ensuring reliability and correctness

Cons

  • May have a learning curve for complex configurations
  • Performance can be impacted when processing large amounts of HTML
  • Limited to Ruby ecosystem, not available for other programming languages
  • Might require regular updates to keep up with evolving web security standards

Code Examples

  1. Basic usage:
require 'sanitize'

dirty_html = '<script>alert("XSS!");</script><p>Hello, <strong>world!</strong></p>'
clean_html = Sanitize.fragment(dirty_html)

puts clean_html
# Output: Hello, <strong>world!</strong>
  1. Custom configuration:
custom_config = Sanitize::Config::RESTRICTED.merge(
  elements: Sanitize::Config::RESTRICTED[:elements] + ['img'],
  attributes: {
    'img' => ['src', 'alt']
  }
)

dirty_html = '<p>Check out this <img src="safe-image.jpg" alt="Safe Image" onclick="alert(\'XSS\')"> image!</p>'
clean_html = Sanitize.fragment(dirty_html, custom_config)

puts clean_html
# Output: <p>Check out this <img src="safe-image.jpg" alt="Safe Image"> image!</p>
  1. Transforming elements:
transformers = lambda do |env|
  node = env[:node]
  node_name = env[:node_name]

  if node_name == 'a' && node['href']
    node['rel'] = 'nofollow'
  end

  return node
end

dirty_html = '<a href="http://example.com">Link</a>'
clean_html = Sanitize.fragment(dirty_html, transformers: transformers)

puts clean_html
# Output: <a href="http://example.com" rel="nofollow">Link</a>

Getting Started

To use Sanitize in your Ruby project:

  1. Add to your Gemfile:

    gem 'sanitize'

  2. Run:

    bundle install

  3. In your Ruby code:

    require 'sanitize'

dirty_html = '<script>alert("XSS!");</script><p>Hello, <strong>world!</strong></p>'
clean_html = Sanitize.fragment(dirty_html)

For more advanced usage and configuration options, refer to the official documentation.

Competitor Comparisons

gjtorikian logo

html-pipeline

2,266

HTML processing filters and utilities

Pros of html-pipeline

  • Modular pipeline architecture allows for flexible customization and extension
  • Supports a wide range of transformations beyond just sanitization
  • Integrates well with other Ruby libraries and frameworks

Cons of html-pipeline

  • More complex setup and configuration compared to Sanitize
  • May have a steeper learning curve for simple use cases
  • Potentially higher resource usage due to its broader feature set

Code Comparison

Sanitize:

Sanitize.fragment(html, Sanitize::Config::BASIC)

html-pipeline:

pipeline = HTML::Pipeline.new([
  HTML::Pipeline::SanitizationFilter,
  HTML::Pipeline::AutolinkFilter
])
result = pipeline.call(html)

Key Differences

Sanitize focuses specifically on HTML sanitization, providing a straightforward API for cleaning up potentially unsafe HTML. It's lightweight and easy to use for simple sanitization tasks.

html-pipeline, on the other hand, offers a more comprehensive approach to HTML processing. It allows for chaining multiple filters and transformations, making it suitable for complex content processing workflows. While it includes sanitization capabilities, it extends far beyond that, offering features like syntax highlighting, mention linking, and more.

Choose Sanitize for straightforward HTML sanitization, and html-pipeline for more complex HTML processing pipelines that require multiple transformations.

cure53 logo

DOMPurify

13,621

DOMPurify - a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMPurify works with a secure default, but offers a lot of configurability and hooks. Demo:

Pros of DOMPurify

  • Specifically designed for client-side sanitization, making it more suitable for browser environments
  • Offers better performance and smaller file size, which is crucial for front-end applications
  • Provides more extensive configuration options and flexibility in sanitization rules

Cons of DOMPurify

  • Limited to DOM-based sanitization, which may not be suitable for all use cases
  • Requires a DOM environment to function, making it less versatile for server-side applications

Code Comparison

DOMPurify:

import DOMPurify from 'dompurify';

const dirty = '<script>alert("xss")</script><p>Hello world!</p>';
const clean = DOMPurify.sanitize(dirty);

Sanitize:

require 'sanitize'

dirty = '<script>alert("xss")</script><p>Hello world!</p>'
clean = Sanitize.fragment(dirty)

Both libraries effectively remove the malicious script tag, but DOMPurify operates in JavaScript and is tailored for browser environments, while Sanitize is a Ruby gem more suitable for server-side sanitization.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Sanitize

Sanitize is an allowlist-based HTML and CSS sanitizer. It removes all HTML and/or CSS from a string except the elements, attributes, and properties you choose to allow.

Using a simple configuration syntax, you can tell Sanitize to allow certain HTML elements, certain attributes within those elements, and even certain URL protocols within attributes that contain URLs. You can also allow specific CSS properties, @ rules, and URL protocols in elements or attributes containing CSS. Any HTML or CSS that you don't explicitly allow will be removed.

Sanitize is based on the Nokogiri HTML5 parser, which parses HTML the same way modern browsers do, and Crass, which parses CSS the same way modern browsers do. As long as your allowlist config only allows safe markup and CSS, even the most malformed or malicious input will be transformed into safe output.

Gem Version Tests

Links

Installation

gem install sanitize

Quick Start

require 'sanitize'

# Clean up an HTML fragment using Sanitize's permissive but safe Relaxed config.
# This also sanitizes any CSS in `<style>` elements or `style` attributes.
Sanitize.fragment(html, Sanitize::Config::RELAXED)

# Clean up an HTML document using the Relaxed config.
Sanitize.document(html, Sanitize::Config::RELAXED)

# Clean up a standalone CSS stylesheet using the Relaxed config.
Sanitize::CSS.stylesheet(css, Sanitize::Config::RELAXED)

# Clean up some CSS properties using the Relaxed config.
Sanitize::CSS.properties(css, Sanitize::Config::RELAXED)

Usage

Sanitize can sanitize the following types of input:

  • HTML fragments
  • HTML documents
  • CSS stylesheets inside HTML <style> elements
  • CSS properties inside HTML style attributes
  • Standalone CSS stylesheets
  • Standalone CSS properties

Warning

Sanitize cannot fully sanitize the contents of <math> or <svg> elements. MathML and SVG elements are foreign elements that don't follow normal HTML parsing rules.

By default, Sanitize will remove all MathML and SVG elements. If you add MathML or SVG elements to a custom element allowlist, you may create a security vulnerability in your application.

HTML Fragments

A fragment is a snippet of HTML that doesn't contain a root-level <html> element.

If you don't specify any configuration options, Sanitize will use its strictest settings by default, which means it will strip all HTML and leave only safe text behind.

html = '<b><a href="http://foo.com/">foo</a></b><img src="bar.jpg">'
Sanitize.fragment(html)
# => 'foo'

To keep certain elements, add them to the element allowlist.

Sanitize.fragment(html, :elements => ['b'])
# => '<b>foo</b>'

HTML Documents

When sanitizing a document, the <html> element must be allowlisted. You can also set :allow_doctype to true to allow well-formed document type definitions.

html = %[
  <!DOCTYPE html>
  <html>
    <b><a href="http://foo.com/">foo</a></b><img src="bar.jpg">
  </html>
]

Sanitize.document(html,
  :allow_doctype => true,
  :elements      => ['html']
)
# => %[
#      <!DOCTYPE html><html>foo
#
#      </html>
#    ]

CSS in HTML

To sanitize CSS in an HTML fragment or document, first allowlist the <style> element and/or the style attribute. Then allowlist the CSS properties, @ rules, and URL protocols you wish to allow. You can also choose whether to allow CSS comments or browser compatibility hacks.

html = %[
  <style>
    div { color: green; width: 1024px; }
  </style>

  <div style="height: 100px; width: 100px;"></div>
  <p>hello!</p>
]

Sanitize.fragment(html,
  :elements   => ['div', 'style'],
  :attributes => {'div' => ['style']},

  :css => {
    :properties => ['width']
  }
)
#=> %[
#   <style>
#     div {  width: 1024px; }
#   </style>
#
#   <div style=" width: 100px;"></div>
#   hello!
# ]

Standalone CSS

Sanitize will happily clean up a standalone CSS stylesheet or property string without needing to invoke the HTML parser.

css = %[
  @import url(evil.css);

  a { text-decoration: none; }

  a:hover {
    left: expression(alert('xss!'));
    text-decoration: underline;
  }
]

Sanitize::CSS.stylesheet(css, Sanitize::Config::RELAXED)
# => %[
#
#
#
#   a { text-decoration: none; }
#
#   a:hover {
#
#     text-decoration: underline;
#   }
# ]

Sanitize::CSS.properties(%[
  left: expression(alert('xss!'));
  text-decoration: underline;
], Sanitize::Config::RELAXED)
# => %[
#
#   text-decoration: underline;
# ]

Configuration

In addition to the ultra-safe default settings, Sanitize comes with three other built-in configurations that you can use out of the box or adapt to meet your needs.

Sanitize::Config::RESTRICTED

Allows only very simple inline markup. No links, images, or block elements.

Sanitize.fragment(html, Sanitize::Config::RESTRICTED)
# => '<b>foo</b>'

Sanitize::Config::BASIC

Allows a variety of markup including formatting elements, links, and lists.

Images and tables are not allowed, links are limited to FTP, HTTP, HTTPS, and mailto protocols, and a rel="nofollow" attribute is added to all links to mitigate SEO spam.

Sanitize.fragment(html, Sanitize::Config::BASIC)
# => '<b><a href="http://foo.com/" rel="nofollow">foo</a></b>'

Sanitize::Config::RELAXED

Allows an even wider variety of markup, including images and tables, as well as safe CSS. Links are still limited to FTP, HTTP, HTTPS, and mailto protocols, while images are limited to HTTP and HTTPS. In this mode, rel="nofollow" is not added to links.

Sanitize.fragment(html, Sanitize::Config::RELAXED)
# => '<b><a href="http://foo.com/">foo</a></b><img src="bar.jpg">'

Custom Configuration

If the built-in modes don't meet your needs, you can easily specify a custom configuration:

Sanitize.fragment(html,
  :elements => ['a', 'span'],

  :attributes => {
    'a'    => ['href', 'title'],
    'span' => ['class']
  },

  :protocols => {
    'a' => {'href' => ['http', 'https', 'mailto']}
  }
)

You can also start with one of Sanitize's built-in configurations and then customize it to meet your needs.

The built-in configs are deeply frozen to prevent people from modifying them (either accidentally or maliciously). To customize a built-in config, create a new copy using Sanitize::Config.merge(), like so:

# Create a customized copy of the Basic config, adding <div> and <table> to the
# existing allowlisted elements.
Sanitize.fragment(html, Sanitize::Config.merge(Sanitize::Config::BASIC,
  :elements        => Sanitize::Config::BASIC[:elements] + ['div', 'table'],
  :remove_contents => true
))

The example above adds the <div> and <table> elements to a copy of the existing list of elements in Sanitize::Config::BASIC. If you instead want to completely overwrite the elements array with your own, you can omit the + operation:

# Overwrite :elements instead of creating a copy with new entries.
Sanitize.fragment(html, Sanitize::Config.merge(Sanitize::Config::BASIC,
  :elements        => ['div', 'table'],
  :remove_contents => true
))

Config Settings

:add_attributes (Hash)

Attributes to add to specific elements. If the attribute already exists, it will be replaced with the value specified here. Specify all element names and attributes in lowercase.

:add_attributes => {
  'a' => {'rel' => 'nofollow'}
}

:allow_comments (boolean)

Whether or not to allow HTML comments. Allowing comments is strongly discouraged, since IE allows script execution within conditional comments. The default value is false.

:allow_doctype (boolean)

Whether or not to allow well-formed HTML doctype declarations such as "" when sanitizing a document. This setting is ignored when sanitizing fragments. The default value is false.

:attributes (Hash)

Attributes to allow on specific elements. Specify all element names and attributes in lowercase.

:attributes => {
  'a'          => ['href', 'title'],
  'blockquote' => ['cite'],
  'img'        => ['alt', 'src', 'title']
}

If you'd like to allow certain attributes on all elements, use the symbol :all instead of an element name.

# Allow the class attribute on all elements.
:attributes => {
  :all => ['class'],
  'a'  => ['href', 'title']
}

To allow arbitrary HTML5 data-* attributes, use the symbol :data in place of an attribute name.

# Allow arbitrary HTML5 data-* attributes on <div> elements.
:attributes => {
  'div' => [:data]
}

:css (Hash)

Hash of the following CSS config settings to be used when sanitizing CSS (either standalone or embedded in HTML).

:css => :allow_comments (boolean)

Whether or not to allow CSS comments. The default value is false.

:css => :allow_hacks (boolean)

Whether or not to allow browser compatibility hacks such as the IE * and _ hacks. These are generally harmless, but technically result in invalid CSS. The default is false.

:css => :at_rules (Array or Set)

Names of CSS at-rules to allow that may not have associated blocks, such as import or charset. Names should be specified in lowercase.

:css => :at_rules_with_properties (Array or Set)

Names of CSS at-rules to allow that may have associated blocks containing CSS properties. At-rules like font-face and page fall into this category. Names should be specified in lowercase.

:css => :at_rules_with_styles (Array or Set)

Names of CSS at-rules to allow that may have associated blocks containing style rules. At-rules like media and keyframes fall into this category. Names should be specified in lowercase.

:css => :import_url_validator

This is a Proc (or other callable object) that will be called and passed the URL specified for any @import at-rules.

You can use this to limit what can be imported, for example something like the following to limit @import to Google Fonts URLs:

Proc.new { |url| url.start_with?("https://fonts.googleapis.com") }
:css => :properties (Array or Set)

List of CSS property names to allow. Names should be specified in lowercase.

:css => :protocols (Array or Set)

URL protocols to allow in CSS URLs. Should be specified in lowercase.

If you'd like to allow the use of relative URLs which don't have a protocol, include the symbol :relative in the protocol array.

:elements (Array or Set)

Array of HTML element names to allow. Specify all names in lowercase. Any elements not in this array will be removed.

:elements => %w[
  a abbr b blockquote br cite code dd dfn dl dt em i kbd li mark ol p pre
  q s samp small strike strong sub sup time u ul var
]

Warning

Sanitize cannot fully sanitize the contents of <math> or <svg> elements. MathML and SVG elements are foreign elements that don't follow normal HTML parsing rules.

By default, Sanitize will remove all MathML and SVG elements. If you add MathML or SVG elements to a custom element allowlist, you must assume that any content inside them will be allowed, even if that content would otherwise be removed or escaped by Sanitize. This may create a security vulnerability in your application.

Note

Sanitize always removes <noscript> elements and their contents, even if noscript is in the allowlist.

This is because a <noscript> element's content is parsed differently in browsers depending on whether or not scripting is enabled. Since Nokogiri doesn't support scripting, it always parses <noscript> elements as if scripting is disabled. This results in edge cases where it's not possible to reliably sanitize the contents of a <noscript> element because Nokogiri can't fully replicate the parsing behavior of a scripting-enabled browser.

:parser_options (Hash)

Parsing options to be supplied to nokogumbo.

:parser_options => {
  max_errors: -1,
  max_tree_depth: -1
}

:protocols (Hash)

URL protocols to allow in specific attributes. If an attribute is listed here and contains a protocol other than those specified (or if it contains no protocol at all), it will be removed.

:protocols => {
  'a'   => {'href' => ['ftp', 'http', 'https', 'mailto']},
  'img' => {'src'  => ['http', 'https']}
}

If you'd like to allow the use of relative URLs which don't have a protocol, include the symbol :relative in the protocol array:

:protocols => {
  'a' => {'href' => ['http', 'https', :relative]}
}

:remove_contents (boolean or Array or Set)

If this is true, Sanitize will remove the contents of any non-allowlisted elements in addition to the elements themselves. By default, Sanitize leaves the safe parts of an element's contents behind when the element is removed.

If this is an Array or Set of element names, then only the contents of the specified elements (when filtered) will be removed, and the contents of all other filtered elements will be left behind.

The default value is %w[iframe math noembed noframes noscript plaintext script style svg xmp].

:transformers (Array or callable)

Custom HTML transformer or array of custom transformers. See the Transformers section below for details.

:whitespace_elements (Hash)

Hash of element names which, when removed, should have their contents surrounded by whitespace to preserve readability.

Each element name is a key pointing to another Hash, which provides the specific whitespace that should be inserted :before and :after the removed element's position. The :after value will only be inserted if the removed element has children, in which case it will be inserted after those children.

:whitespace_elements => {
  'br'  => { :before => "\n", :after => "" },
  'div' => { :before => "\n", :after => "\n" },
  'p'   => { :before => "\n", :after => "\n" }
}

The default elements with whitespace added before and after are:

address article aside blockquote br dd div dl dt
footer h1 h2 h3 h4 h5 h6 header hgroup hr li nav
ol p pre section ul

Transformers

Transformers allow you to filter and modify HTML nodes using your own custom logic, on top of (or instead of) Sanitize's core filter. A transformer is any object that responds to call() (such as a lambda or proc).

To use one or more transformers, pass them to the :transformers config setting. You may pass a single transformer or an array of transformers.

Sanitize.fragment(html, :transformers => [
  transformer_one,
  transformer_two
])

Input

Each transformer's call() method will be called once for each node in the HTML (including elements, text nodes, comments, etc.), and will receive as an argument a Hash that contains the following items:

  • :config - The current Sanitize configuration Hash.

  • :is_allowlisted - true if the current node has been allowlisted by a previous transformer, false otherwise. It's generally bad form to remove a node that a previous transformer has allowlisted.

  • :node - A Nokogiri::XML::Node object representing an HTML node. The node may be an element, a text node, a comment, a CDATA node, or a document fragment. Use Nokogiri's inspection methods (element?, text?, etc.) to selectively ignore node types you aren't interested in.

  • :node_allowlist - Set of Nokogiri::XML::Node objects in the current document that have been allowlisted by previous transformers, if any. It's generally bad form to remove a node that a previous transformer has allowlisted.

  • :node_name - The name of the current HTML node, always lowercase (e.g. "div" or "span"). For non-element nodes, the name will be something like "text", "comment", "#cdata-section", "#document-fragment", etc.

Output

A transformer doesn't have to return anything, but may optionally return a Hash, which may contain the following items:

  • :node_allowlist - Array or Set of specific Nokogiri::XML::Node objects to add to the document's allowlist, bypassing the current Sanitize config. These specific nodes and all their attributes will be allowlisted, but their children will not be.

If a transformer returns anything other than a Hash, the return value will be ignored.

Processing

Each transformer has full access to the Nokogiri::XML::Node that's passed into it and to the rest of the document via the node's document() method. Any changes made to the current node or to the document will be reflected instantly in the document and passed on to subsequently called transformers and to Sanitize itself. A transformer may even call Sanitize internally to perform custom sanitization if needed.

Nodes are passed into transformers in the order in which they're traversed. Sanitize performs top-down traversal, meaning that nodes are traversed in the same order you'd read them in the HTML, starting at the top node, then its first child, and so on.

html = %[
  <header>
    <span>
      <strong>foo</strong>
    </span>
    <p>bar</p>
  </header>

  <footer></footer>
]

transformer = lambda do |env|
  puts env[:node_name] if env[:node].element?
end

# Prints "header", "span", "strong", "p", "footer".
Sanitize.fragment(html, :transformers => transformer)

Transformers have a tremendous amount of power, including the power to completely bypass Sanitize's built-in filtering. Be careful! Your safety is in your own hands.

Example: Transformer to allow image URLs by domain

The following example demonstrates how to remove image elements unless they use a relative URL or are hosted on a specific domain. It assumes that the <img> element and its src attribute are already allowlisted.

require 'uri'

image_allowlist_transformer = lambda do |env|
  # Ignore everything except <img> elements.
  return unless env[:node_name] == 'img'

  node      = env[:node]
  image_uri = URI.parse(node['src'])

  # Only allow relative URLs or URLs with the example.com domain. The
  # image_uri.host.nil? check ensures that protocol-relative URLs like
  # "//evil.com/foo.jpg".
  unless image_uri.host == 'example.com' || (image_uri.host.nil? && image_uri.relative?)
    node.unlink # `Nokogiri::XML::Node#unlink` removes a node from the document
  end
end

Example: Transformer to allow YouTube video embeds

The following example demonstrates how to create a transformer that will safely allow valid YouTube video embeds without having to allow other kinds of embedded content, which would be the case if you tried to do this by just allowing all <iframe> elements:

youtube_transformer = lambda do |env|
  node      = env[:node]
  node_name = env[:node_name]

  # Don't continue if this node is already allowlisted or is not an element.
  return if env[:is_allowlisted] || !node.element?

  # Don't continue unless the node is an iframe.
  return unless node_name == 'iframe'

  # Verify that the video URL is actually a valid YouTube video URL.
  return unless node['src'] =~ %r|\A(?:https?:)?//(?:www\.)?youtube(?:-nocookie)?\.com/|

  # We're now certain that this is a YouTube embed, but we still need to run
  # it through a special Sanitize step to ensure that no unwanted elements or
  # attributes that don't belong in a YouTube embed can sneak in.
  Sanitize.node!(node, {
    :elements => %w[iframe],

    :attributes => {
      'iframe'  => %w[allowfullscreen frameborder height src width]
    }
  })

  # Now that we're sure that this is a valid YouTube embed and that there are
  # no unwanted elements or attributes hidden inside it, we can tell Sanitize
  # to allowlist the current node.
  {:node_allowlist => [node]}
end

html = %[
<iframe width="420" height="315" src="//www.youtube.com/embed/dQw4w9WgXcQ"
    frameborder="0" allowfullscreen></iframe>
]

Sanitize.fragment(html, :transformers => youtube_transformer)
# => '<iframe width="420" height="315" src="//www.youtube.com/embed/dQw4w9WgXcQ" frameborder="0" allowfullscreen=""></iframe>'

NPM DownloadsLast 30 Days