Package Exports

eslint-plugin-xss

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-plugin-xss) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

eslint-plugin-xss

Validates M-Files coding conventions

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install eslint-plugin-xss:

$ npm install eslint-plugin-xss --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-xss globally.

Usage

Add xss to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
    "plugins": [
        "xss"
    ]
}

Then configure the rules you want to use under the rules section.

{
    "rules": {
        "xss/rule-name": 2
    }
}

Supported Rules

###xss/no-mixed-html

"xss/no-mixed-html": [ 2, {
    "encoders": [ "utils.htmlEncode()", "CSS.escape()", "Number()" ],
    "unsafe": [ ".html()" ]
} ];

The rule disallows mixing HTML content and unencoded input. It should fail in following scenarios:

var x = '<div>' + input + '</div>';
$node.html( '<div>' + input + '</div>' );

The rule also uses variable names to convey meaning about the contents. Variable names with 'html' are expected to be html encoded. The following will fail:

var html = input;
var text = htmlInput;
displayValue( htmlInput );
htmlItems = [ input1, input2 ].join();
textItems = [ '<div>', input, '</div>' ].join();
tag = isNumbered ? '<ol>' : '<ul>';