Installations

npm install eslint-plugin-xss

Pull Requests

Open

2

Total

8

Closed

1

Merged

5

Issues

Open

4

Total

7

Closed

3

Releases

Unable to fetch releases

Developer

Rantanen

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=0.10.0

Typescript Support

No

Node Version

17.3.0

NPM Version

8.3.0 Statistics

66 Stars

51 Commits

16 Forks

2 Watching

1 Branches

5 Contributors

Updated on 01 Oct 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

14,945,590

Last day

1%

11,471

Compared to previous day

Last week

2.7%

68,249

Compared to previous week

Last month

4.6%

260,908

Compared to previous month

Last year

9.3%

2,770,846

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

requireindex

Dev Dependencies

3

eslint mocha mochawesome

Versions

eslint-plugin-xss

Tries to detect XSS issues in codebase before they end up in production.

Installation

You'll first need to install ESLint:

$ npm install 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:

1{
2    "plugins": [
3        "xss"
4    ]
5}

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

1{
2    "rules": {
3        "xss/rule-name": 2
4    }
5}

Or:

Enable all rules by adding the following to your .eslintrc configuration file

1{
2    "extends": [
3        "plugin:xss/recommended"
4    ]
5}

Supported Rules

xss/no-mixed-html: Warn about possible XSS issues.
xss/no-location-href-assign: Warn when trying to modify location.href.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

9

License

Determines if the project has defined a license.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More