mirror of
https://github.com/nunocoracao/blowfish.git
synced 2026-01-30 16:31:52 +01:00
config redirect
This commit is contained in:
Nuno Coração
378
node_modules/dompurify/LICENSE
generated
vendored
Normal file
378
node_modules/dompurify/LICENSE
generated
vendored
Normal file
@@ -0,0 +1,378 @@
|
||||
DOMPurify
|
||||
Copyright 2015 Mario Heiderich
|
||||
|
||||
DOMPurify is free software; you can redistribute it and/or modify it under the
|
||||
terms of either:
|
||||
|
||||
a) the Apache License Version 2.0, or
|
||||
b) the Mozilla Public License Version 2.0
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
|
||||
-----------------------------------------------------------------------------
|
||||
Mozilla Public License, version 2.0
|
||||
|
||||
1. Definitions
|
||||
|
||||
1.1. “Contributor”
|
||||
|
||||
means each individual or legal entity that creates, contributes to the
|
||||
creation of, or owns Covered Software.
|
||||
|
||||
1.2. “Contributor Version”
|
||||
|
||||
means the combination of the Contributions of others (if any) used by a
|
||||
Contributor and that particular Contributor’s Contribution.
|
||||
|
||||
1.3. “Contribution”
|
||||
|
||||
means Covered Software of a particular Contributor.
|
||||
|
||||
1.4. “Covered Software”
|
||||
|
||||
means Source Code Form to which the initial Contributor has attached the
|
||||
notice in Exhibit A, the Executable Form of such Source Code Form, and
|
||||
Modifications of such Source Code Form, in each case including portions
|
||||
thereof.
|
||||
|
||||
1.5. “Incompatible With Secondary Licenses”
|
||||
means
|
||||
|
||||
a. that the initial Contributor has attached the notice described in
|
||||
Exhibit B to the Covered Software; or
|
||||
|
||||
b. that the Covered Software was made available under the terms of version
|
||||
1.1 or earlier of the License, but not also under the terms of a
|
||||
Secondary License.
|
||||
|
||||
1.6. “Executable Form”
|
||||
|
||||
means any form of the work other than Source Code Form.
|
||||
|
||||
1.7. “Larger Work”
|
||||
|
||||
means a work that combines Covered Software with other material, in a separate
|
||||
file or files, that is not Covered Software.
|
||||
|
||||
1.8. “License”
|
||||
|
||||
means this document.
|
||||
|
||||
1.9. “Licensable”
|
||||
|
||||
means having the right to grant, to the maximum extent possible, whether at the
|
||||
time of the initial grant or subsequently, any and all of the rights conveyed by
|
||||
this License.
|
||||
|
||||
1.10. “Modifications”
|
||||
|
||||
means any of the following:
|
||||
|
||||
a. any file in Source Code Form that results from an addition to, deletion
|
||||
from, or modification of the contents of Covered Software; or
|
||||
|
||||
b. any new file in Source Code Form that contains any Covered Software.
|
||||
|
||||
1.11. “Patent Claims” of a Contributor
|
||||
|
||||
means any patent claim(s), including without limitation, method, process,
|
||||
and apparatus claims, in any patent Licensable by such Contributor that
|
||||
would be infringed, but for the grant of the License, by the making,
|
||||
using, selling, offering for sale, having made, import, or transfer of
|
||||
either its Contributions or its Contributor Version.
|
||||
|
||||
1.12. “Secondary License”
|
||||
|
||||
means either the GNU General Public License, Version 2.0, the GNU Lesser
|
||||
General Public License, Version 2.1, the GNU Affero General Public
|
||||
License, Version 3.0, or any later versions of those licenses.
|
||||
|
||||
1.13. “Source Code Form”
|
||||
|
||||
means the form of the work preferred for making modifications.
|
||||
|
||||
1.14. “You” (or “Your”)
|
||||
|
||||
means an individual or a legal entity exercising rights under this
|
||||
License. For legal entities, “You” includes any entity that controls, is
|
||||
controlled by, or is under common control with You. For purposes of this
|
||||
definition, “control” means (a) the power, direct or indirect, to cause
|
||||
the direction or management of such entity, whether by contract or
|
||||
otherwise, or (b) ownership of more than fifty percent (50%) of the
|
||||
outstanding shares or beneficial ownership of such entity.
|
||||
|
||||
|
||||
2. License Grants and Conditions
|
||||
|
||||
2.1. Grants
|
||||
|
||||
Each Contributor hereby grants You a world-wide, royalty-free,
|
||||
non-exclusive license:
|
||||
|
||||
a. under intellectual property rights (other than patent or trademark)
|
||||
Licensable by such Contributor to use, reproduce, make available,
|
||||
modify, display, perform, distribute, and otherwise exploit its
|
||||
Contributions, either on an unmodified basis, with Modifications, or as
|
||||
part of a Larger Work; and
|
||||
|
||||
b. under Patent Claims of such Contributor to make, use, sell, offer for
|
||||
sale, have made, import, and otherwise transfer either its Contributions
|
||||
or its Contributor Version.
|
||||
|
||||
2.2. Effective Date
|
||||
|
||||
The licenses granted in Section 2.1 with respect to any Contribution become
|
||||
effective for each Contribution on the date the Contributor first distributes
|
||||
such Contribution.
|
||||
|
||||
2.3. Limitations on Grant Scope
|
||||
|
||||
The licenses granted in this Section 2 are the only rights granted under this
|
||||
License. No additional rights or licenses will be implied from the distribution
|
||||
or licensing of Covered Software under this License. Notwithstanding Section
|
||||
2.1(b) above, no patent license is granted by a Contributor:
|
||||
|
||||
a. for any code that a Contributor has removed from Covered Software; or
|
||||
|
||||
b. for infringements caused by: (i) Your and any other third party’s
|
||||
modifications of Covered Software, or (ii) the combination of its
|
||||
Contributions with other software (except as part of its Contributor
|
||||
Version); or
|
||||
|
||||
c. under Patent Claims infringed by Covered Software in the absence of its
|
||||
Contributions.
|
||||
|
||||
This License does not grant any rights in the trademarks, service marks, or
|
||||
logos of any Contributor (except as may be necessary to comply with the
|
||||
notice requirements in Section 3.4).
|
||||
|
||||
2.4. Subsequent Licenses
|
||||
|
||||
No Contributor makes additional grants as a result of Your choice to
|
||||
distribute the Covered Software under a subsequent version of this License
|
||||
(see Section 10.2) or under the terms of a Secondary License (if permitted
|
||||
under the terms of Section 3.3).
|
||||
|
||||
2.5. Representation
|
||||
|
||||
Each Contributor represents that the Contributor believes its Contributions
|
||||
are its original creation(s) or it has sufficient rights to grant the
|
||||
rights to its Contributions conveyed by this License.
|
||||
|
||||
2.6. Fair Use
|
||||
|
||||
This License is not intended to limit any rights You have under applicable
|
||||
copyright doctrines of fair use, fair dealing, or other equivalents.
|
||||
|
||||
2.7. Conditions
|
||||
|
||||
Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in
|
||||
Section 2.1.
|
||||
|
||||
|
||||
3. Responsibilities
|
||||
|
||||
3.1. Distribution of Source Form
|
||||
|
||||
All distribution of Covered Software in Source Code Form, including any
|
||||
Modifications that You create or to which You contribute, must be under the
|
||||
terms of this License. You must inform recipients that the Source Code Form
|
||||
of the Covered Software is governed by the terms of this License, and how
|
||||
they can obtain a copy of this License. You may not attempt to alter or
|
||||
restrict the recipients’ rights in the Source Code Form.
|
||||
|
||||
3.2. Distribution of Executable Form
|
||||
|
||||
If You distribute Covered Software in Executable Form then:
|
||||
|
||||
a. such Covered Software must also be made available in Source Code Form,
|
||||
as described in Section 3.1, and You must inform recipients of the
|
||||
Executable Form how they can obtain a copy of such Source Code Form by
|
||||
reasonable means in a timely manner, at a charge no more than the cost
|
||||
of distribution to the recipient; and
|
||||
|
||||
b. You may distribute such Executable Form under the terms of this License,
|
||||
or sublicense it under different terms, provided that the license for
|
||||
the Executable Form does not attempt to limit or alter the recipients’
|
||||
rights in the Source Code Form under this License.
|
||||
|
||||
3.3. Distribution of a Larger Work
|
||||
|
||||
You may create and distribute a Larger Work under terms of Your choice,
|
||||
provided that You also comply with the requirements of this License for the
|
||||
Covered Software. If the Larger Work is a combination of Covered Software
|
||||
with a work governed by one or more Secondary Licenses, and the Covered
|
||||
Software is not Incompatible With Secondary Licenses, this License permits
|
||||
You to additionally distribute such Covered Software under the terms of
|
||||
such Secondary License(s), so that the recipient of the Larger Work may, at
|
||||
their option, further distribute the Covered Software under the terms of
|
||||
either this License or such Secondary License(s).
|
||||
|
||||
3.4. Notices
|
||||
|
||||
You may not remove or alter the substance of any license notices (including
|
||||
copyright notices, patent notices, disclaimers of warranty, or limitations
|
||||
of liability) contained within the Source Code Form of the Covered
|
||||
Software, except that You may alter any license notices to the extent
|
||||
required to remedy known factual inaccuracies.
|
||||
|
||||
3.5. Application of Additional Terms
|
||||
|
||||
You may choose to offer, and to charge a fee for, warranty, support,
|
||||
indemnity or liability obligations to one or more recipients of Covered
|
||||
Software. However, You may do so only on Your own behalf, and not on behalf
|
||||
of any Contributor. You must make it absolutely clear that any such
|
||||
warranty, support, indemnity, or liability obligation is offered by You
|
||||
alone, and You hereby agree to indemnify every Contributor for any
|
||||
liability incurred by such Contributor as a result of warranty, support,
|
||||
indemnity or liability terms You offer. You may include additional
|
||||
disclaimers of warranty and limitations of liability specific to any
|
||||
jurisdiction.
|
||||
|
||||
4. Inability to Comply Due to Statute or Regulation
|
||||
|
||||
If it is impossible for You to comply with any of the terms of this License
|
||||
with respect to some or all of the Covered Software due to statute, judicial
|
||||
order, or regulation then You must: (a) comply with the terms of this License
|
||||
to the maximum extent possible; and (b) describe the limitations and the code
|
||||
they affect. Such description must be placed in a text file included with all
|
||||
distributions of the Covered Software under this License. Except to the
|
||||
extent prohibited by statute or regulation, such description must be
|
||||
sufficiently detailed for a recipient of ordinary skill to be able to
|
||||
understand it.
|
||||
|
||||
5. Termination
|
||||
|
||||
5.1. The rights granted under this License will terminate automatically if You
|
||||
fail to comply with any of its terms. However, if You become compliant,
|
||||
then the rights granted under this License from a particular Contributor
|
||||
are reinstated (a) provisionally, unless and until such Contributor
|
||||
explicitly and finally terminates Your grants, and (b) on an ongoing basis,
|
||||
if such Contributor fails to notify You of the non-compliance by some
|
||||
reasonable means prior to 60 days after You have come back into compliance.
|
||||
Moreover, Your grants from a particular Contributor are reinstated on an
|
||||
ongoing basis if such Contributor notifies You of the non-compliance by
|
||||
some reasonable means, this is the first time You have received notice of
|
||||
non-compliance with this License from such Contributor, and You become
|
||||
compliant prior to 30 days after Your receipt of the notice.
|
||||
|
||||
5.2. If You initiate litigation against any entity by asserting a patent
|
||||
infringement claim (excluding declaratory judgment actions, counter-claims,
|
||||
and cross-claims) alleging that a Contributor Version directly or
|
||||
indirectly infringes any patent, then the rights granted to You by any and
|
||||
all Contributors for the Covered Software under Section 2.1 of this License
|
||||
shall terminate.
|
||||
|
||||
5.3. In the event of termination under Sections 5.1 or 5.2 above, all end user
|
||||
license agreements (excluding distributors and resellers) which have been
|
||||
validly granted by You or Your distributors under this License prior to
|
||||
termination shall survive termination.
|
||||
|
||||
6. Disclaimer of Warranty
|
||||
|
||||
Covered Software is provided under this License on an “as is” basis, without
|
||||
warranty of any kind, either expressed, implied, or statutory, including,
|
||||
without limitation, warranties that the Covered Software is free of defects,
|
||||
merchantable, fit for a particular purpose or non-infringing. The entire
|
||||
risk as to the quality and performance of the Covered Software is with You.
|
||||
Should any Covered Software prove defective in any respect, You (not any
|
||||
Contributor) assume the cost of any necessary servicing, repair, or
|
||||
correction. This disclaimer of warranty constitutes an essential part of this
|
||||
License. No use of any Covered Software is authorized under this License
|
||||
except under this disclaimer.
|
||||
|
||||
7. Limitation of Liability
|
||||
|
||||
Under no circumstances and under no legal theory, whether tort (including
|
||||
negligence), contract, or otherwise, shall any Contributor, or anyone who
|
||||
distributes Covered Software as permitted above, be liable to You for any
|
||||
direct, indirect, special, incidental, or consequential damages of any
|
||||
character including, without limitation, damages for lost profits, loss of
|
||||
goodwill, work stoppage, computer failure or malfunction, or any and all
|
||||
other commercial damages or losses, even if such party shall have been
|
||||
informed of the possibility of such damages. This limitation of liability
|
||||
shall not apply to liability for death or personal injury resulting from such
|
||||
party’s negligence to the extent applicable law prohibits such limitation.
|
||||
Some jurisdictions do not allow the exclusion or limitation of incidental or
|
||||
consequential damages, so this exclusion and limitation may not apply to You.
|
||||
|
||||
8. Litigation
|
||||
|
||||
Any litigation relating to this License may be brought only in the courts of
|
||||
a jurisdiction where the defendant maintains its principal place of business
|
||||
and such litigation shall be governed by laws of that jurisdiction, without
|
||||
reference to its conflict-of-law provisions. Nothing in this Section shall
|
||||
prevent a party’s ability to bring cross-claims or counter-claims.
|
||||
|
||||
9. Miscellaneous
|
||||
|
||||
This License represents the complete agreement concerning the subject matter
|
||||
hereof. If any provision of this License is held to be unenforceable, such
|
||||
provision shall be reformed only to the extent necessary to make it
|
||||
enforceable. Any law or regulation which provides that the language of a
|
||||
contract shall be construed against the drafter shall not be used to construe
|
||||
this License against a Contributor.
|
||||
|
||||
|
||||
10. Versions of the License
|
||||
|
||||
10.1. New Versions
|
||||
|
||||
Mozilla Foundation is the license steward. Except as provided in Section
|
||||
10.3, no one other than the license steward has the right to modify or
|
||||
publish new versions of this License. Each version will be given a
|
||||
distinguishing version number.
|
||||
|
||||
10.2. Effect of New Versions
|
||||
|
||||
You may distribute the Covered Software under the terms of the version of
|
||||
the License under which You originally received the Covered Software, or
|
||||
under the terms of any subsequent version published by the license
|
||||
steward.
|
||||
|
||||
10.3. Modified Versions
|
||||
|
||||
If you create software not governed by this License, and you want to
|
||||
create a new license for such software, you may create and use a modified
|
||||
version of this License if you rename the license and remove any
|
||||
references to the name of the license steward (except to note that such
|
||||
modified license differs from this License).
|
||||
|
||||
10.4. Distributing Source Code Form that is Incompatible With Secondary Licenses
|
||||
If You choose to distribute Source Code Form that is Incompatible With
|
||||
Secondary Licenses under the terms of this version of the License, the
|
||||
notice described in Exhibit B of this License must be attached.
|
||||
|
||||
Exhibit A - Source Code Form License Notice
|
||||
|
||||
This Source Code Form is subject to the
|
||||
terms of the Mozilla Public License, v.
|
||||
2.0. If a copy of the MPL was not
|
||||
distributed with this file, You can
|
||||
obtain one at
|
||||
http://mozilla.org/MPL/2.0/.
|
||||
|
||||
If it is not possible or desirable to put the notice in a particular file, then
|
||||
You may include the notice in a location (such as a LICENSE file in a relevant
|
||||
directory) where a recipient would be likely to look for such a notice.
|
||||
|
||||
You may add additional accurate notices of copyright ownership.
|
||||
|
||||
Exhibit B - “Incompatible With Secondary Licenses” Notice
|
||||
|
||||
This Source Code Form is “Incompatible
|
||||
With Secondary Licenses”, as defined by
|
||||
the Mozilla Public License, v. 2.0.
|
||||
|
||||
418
node_modules/dompurify/README.md
generated
vendored
Normal file
418
node_modules/dompurify/README.md
generated
vendored
Normal file
@@ -0,0 +1,418 @@
|
||||
# DOMPurify
|
||||
|
||||
[](http://badge.fury.io/js/dompurify)  [](https://www.npmjs.com/package/dompurify) [](https://cdn.jsdelivr.net/npm/dompurify/dist/purify.min.js) [](https://packagephobia.now.sh/result?p=dompurify) [](https://github.com/cure53/DOMPurify/network/dependents)
|
||||
|
||||
[](https://nodei.co/npm/dompurify/)
|
||||
|
||||
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG.
|
||||
|
||||
It's also very simple to use and get started with. DOMPurify was [started in February 2014](https://github.com/cure53/DOMPurify/commit/a630922616927373485e0e787ab19e73e3691b2b) and, meanwhile, has reached version 2.4.1.
|
||||
|
||||
DOMPurify is written in JavaScript and works in all modern browsers (Safari (10+), Opera (15+), Internet Explorer (10+), Edge, Firefox and Chrome - as well as almost anything else using Blink or WebKit). It doesn't break on MSIE6 or other legacy browsers. It either uses [a fall-back](#what-about-older-browsers-like-msie8) or simply does nothing.
|
||||
|
||||
Our automated tests cover [19 different browsers](https://github.com/cure53/DOMPurify/blob/main/test/karma.custom-launchers.config.js#L5) right now, more to come. We also cover Node.js v14.x, v16.x, v17.x and v18.x, running DOMPurify on [jsdom](https://github.com/jsdom/jsdom). Older Node versions are known to work as well, but hey... no guarantees.
|
||||
|
||||
DOMPurify is written by security people who have vast background in web attacks and XSS. Fear not. For more details please also read about our [Security Goals & Threat Model](https://github.com/cure53/DOMPurify/wiki/Security-Goals-&-Threat-Model). Please, read it. Like, really.
|
||||
|
||||
## What does it do?
|
||||
|
||||
DOMPurify sanitizes HTML and prevents XSS attacks. You can feed DOMPurify with string full of dirty HTML and it will return a string (unless configured otherwise) with clean HTML. DOMPurify will strip out everything that contains dangerous HTML and thereby prevent XSS attacks and other nastiness. It's also damn bloody fast. We use the technologies the browser provides and turn them into an XSS filter. The faster your browser, the faster DOMPurify will be.
|
||||
|
||||
## How do I use it?
|
||||
|
||||
It's easy. Just include DOMPurify on your website.
|
||||
|
||||
### Using the unminified development version
|
||||
|
||||
```html
|
||||
<script type="text/javascript" src="src/purify.js"></script>
|
||||
```
|
||||
|
||||
### Using the minified and tested production version (source-map available)
|
||||
|
||||
```html
|
||||
<script type="text/javascript" src="dist/purify.min.js"></script>
|
||||
```
|
||||
|
||||
Afterwards you can sanitize strings by executing the following code:
|
||||
|
||||
```js
|
||||
let clean = DOMPurify.sanitize(dirty);
|
||||
```
|
||||
|
||||
Or maybe this, if you love working with Angular or alike:
|
||||
|
||||
```js
|
||||
import * as DOMPurify from 'dompurify';
|
||||
|
||||
let clean = DOMPurify.sanitize('<b>hello there</b>');
|
||||
```
|
||||
|
||||
The resulting HTML can be written into a DOM element using `innerHTML` or the DOM using `document.write()`. That is fully up to you.
|
||||
Note that by default, we permit HTML, SVG **and** MathML. If you only need HTML, which might be a very common use-case, you can easily set that up as well:
|
||||
|
||||
```js
|
||||
let clean = DOMPurify.sanitize(dirty, { USE_PROFILES: { html: true } });
|
||||
```
|
||||
|
||||
### Where are the TypeScript type definitions?
|
||||
|
||||
They can be found here: [@types/dompurify](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/dompurify)
|
||||
|
||||
### Is there any foot-gun potential?
|
||||
|
||||
Well, please note, if you _first_ sanitize HTML and then modify it _afterwards_, you might easily **void the effects of sanitization**. If you feed the sanitized markup to another library _after_ sanitization, please be certain that the library doesn't mess around with the HTML on its own.
|
||||
|
||||
### Okay, makes sense, let's move on
|
||||
|
||||
After sanitizing your markup, you can also have a look at the property `DOMPurify.removed` and find out, what elements and attributes were thrown out. Please **do not use** this property for making any security critical decisions. This is just a little helper for curious minds.
|
||||
|
||||
### Running DOMPurify on the server
|
||||
|
||||
DOMPurify technically also works server-side with Node.js. Our support strives to follow the [Node.js release cycle](https://nodejs.org/en/about/releases/).
|
||||
|
||||
Running DOMPurify on the server requires a DOM to be present, which is probably no surprise. Usually, [jsdom](https://github.com/jsdom/jsdom) is the tool of choice and we **strongly recommend** to use the latest version of _jsdom_.
|
||||
|
||||
Why? Because older versions of _jsdom_ are known to be buggy in ways that result in XSS _even if_ DOMPurify does everything 100% correctly. There are **known attack vectors** in, e.g. _jsdom v19.0.0_ that are fixed in _jsdom v20.0.0_ - and we really recommend to keep _jsdom_ up to date because of that.
|
||||
|
||||
Other than that, you are fine to use DOMPurify on the server. Probably. This really depends on _jsdom_ or whatever DOM you utilize server-side. If you can live with that, this is how you get it to work:
|
||||
|
||||
```bash
|
||||
npm install dompurify
|
||||
npm install jsdom
|
||||
```
|
||||
|
||||
For _jsdom_ (please use an up-to-date version), this should do the trick:
|
||||
|
||||
```js
|
||||
const createDOMPurify = require('dompurify');
|
||||
const { JSDOM } = require('jsdom');
|
||||
|
||||
const window = new JSDOM('').window;
|
||||
const DOMPurify = createDOMPurify(window);
|
||||
const clean = DOMPurify.sanitize('<b>hello there</b>');
|
||||
```
|
||||
|
||||
Or even this, if you prefer working with imports:
|
||||
|
||||
```js
|
||||
import { JSDOM } from 'jsdom';
|
||||
import DOMPurify from 'dompurify';
|
||||
|
||||
const window = new JSDOM('').window;
|
||||
const purify = DOMPurify(window);
|
||||
const clean = purify.sanitize('<b>hello there</b>');
|
||||
```
|
||||
|
||||
If you have problems making it work in your specific setup, consider looking at the amazing [isomorphic-dompurify](https://github.com/kkomelin/isomorphic-dompurify) project which solves lots of problems people might run into.
|
||||
|
||||
```bash
|
||||
npm install isomorphic-dompurify
|
||||
```
|
||||
|
||||
```js
|
||||
import DOMPurify from 'isomorphic-dompurify';
|
||||
|
||||
const clean = DOMPurify.sanitize('<s>hello</s>');
|
||||
```
|
||||
|
||||
## Is there a demo?
|
||||
|
||||
Of course there is a demo! [Play with DOMPurify](https://cure53.de/purify)
|
||||
|
||||
## What if I find a _security_ bug?
|
||||
|
||||
First of all, please immediately contact us via [email](mailto:mario@cure53.de) so we can work on a fix. [PGP key](https://keyserver.ubuntu.com/pks/lookup?op=vindex&search=0xC26C858090F70ADA)
|
||||
|
||||
Also, you probably qualify for a bug bounty! The fine folks over at [Fastmail](https://www.fastmail.com/) use DOMPurify for their services and added our library to their bug bounty scope. So, if you find a way to bypass or weaken DOMPurify, please also have a look at their website and the [bug bounty info](https://www.fastmail.com/about/bugbounty/).
|
||||
|
||||
## Some purification samples please?
|
||||
|
||||
How does purified markup look like? Well, [the demo](https://cure53.de/purify) shows it for a big bunch of nasty elements. But let's also show some smaller examples!
|
||||
|
||||
```js
|
||||
DOMPurify.sanitize('<img src=x onerror=alert(1)//>'); // becomes <img src="x">
|
||||
DOMPurify.sanitize('<svg><g/onload=alert(2)//<p>'); // becomes <svg><g></g></svg>
|
||||
DOMPurify.sanitize('<p>abc<iframe//src=jAva	script:alert(3)>def</p>'); // becomes <p>abc</p>
|
||||
DOMPurify.sanitize('<math><mi//xlink:href="data:x,<script>alert(4)</script>">'); // becomes <math><mi></mi></math>
|
||||
DOMPurify.sanitize('<TABLE><tr><td>HELLO</tr></TABL>'); // becomes <table><tbody><tr><td>HELLO</td></tr></tbody></table>
|
||||
DOMPurify.sanitize('<UL><li><A HREF=//google.com>click</UL>'); // becomes <ul><li><a href="//google.com">click</a></li></ul>
|
||||
```
|
||||
|
||||
## What is supported?
|
||||
|
||||
DOMPurify currently supports HTML5, SVG and MathML. DOMPurify per default allows CSS, HTML custom data attributes. DOMPurify also supports the Shadow DOM - and sanitizes DOM templates recursively. DOMPurify also allows you to sanitize HTML for being used with the jQuery `$()` and `elm.html()` API without any known problems.
|
||||
|
||||
## What about older browsers like MSIE8?
|
||||
|
||||
DOMPurify offers a fall-back behavior for older MSIE browsers. It uses the MSIE-only `toStaticHTML` feature to sanitize. Note however that in this fall-back mode, pretty much none of the configuration flags shown below have any effect. You need to handle that yourself.
|
||||
|
||||
If not even `toStaticHTML` is supported, DOMPurify does nothing at all. It simply returns exactly the string that you fed it.
|
||||
|
||||
DOMPurify also exposes a property called `isSupported`, which tells you whether DOMPurify will be able to do its job.
|
||||
|
||||
## What about DOMPurify and Trusted Types?
|
||||
|
||||
In version 1.0.9, support for [Trusted Types API](https://github.com/w3c/webappsec-trusted-types) was added to DOMPurify.
|
||||
In version 2.0.0, a config flag was added to control DOMPurify's behavior regarding this.
|
||||
|
||||
When `DOMPurify.sanitize` is used in an environment where the Trusted Types API is available and `RETURN_TRUSTED_TYPE` is set to `true`, it tries to return a `TrustedHTML` value instead of a string (the behavior for `RETURN_DOM` and `RETURN_DOM_FRAGMENT` config options does not change).
|
||||
|
||||
## Can I configure DOMPurify?
|
||||
|
||||
Yes. The included default configuration values are pretty good already - but you can of course override them. Check out the [`/demos`](https://github.com/cure53/DOMPurify/tree/main/demos) folder to see a bunch of examples on how you can [customize DOMPurify](https://github.com/cure53/DOMPurify/tree/main/demos#what-is-this).
|
||||
|
||||
```js
|
||||
/**
|
||||
* General settings
|
||||
*/
|
||||
|
||||
// strip {{ ... }}, ${ ... } and <% ... %> to make output safe for template systems
|
||||
// be careful please, this mode is not recommended for production usage.
|
||||
// allowing template parsing in user-controlled HTML is not advised at all.
|
||||
// only use this mode if there is really no alternative.
|
||||
var clean = DOMPurify.sanitize(dirty, {SAFE_FOR_TEMPLATES: true});
|
||||
|
||||
/**
|
||||
* Control our allow-lists and block-lists
|
||||
*/
|
||||
// allow only <b> elements, very strict
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOWED_TAGS: ['b']});
|
||||
|
||||
// allow only <b> and <q> with style attributes
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOWED_TAGS: ['b', 'q'], ALLOWED_ATTR: ['style']});
|
||||
|
||||
// allow all safe HTML elements but neither SVG nor MathML
|
||||
// note that the USE_PROFILES setting will override the ALLOWED_TAGS setting
|
||||
// so don't use them together
|
||||
var clean = DOMPurify.sanitize(dirty, {USE_PROFILES: {html: true}});
|
||||
|
||||
// allow all safe SVG elements and SVG Filters, no HTML or MathML
|
||||
var clean = DOMPurify.sanitize(dirty, {USE_PROFILES: {svg: true, svgFilters: true}});
|
||||
|
||||
// allow all safe MathML elements and SVG, but no SVG Filters
|
||||
var clean = DOMPurify.sanitize(dirty, {USE_PROFILES: {mathMl: true, svg: true}});
|
||||
|
||||
// change the default namespace from HTML to something different
|
||||
var clean = DOMPurify.sanitize(dirty, {NAMESPACE: 'http://www.w3.org/2000/svg'});
|
||||
|
||||
// leave all safe HTML as it is and add <style> elements to block-list
|
||||
var clean = DOMPurify.sanitize(dirty, {FORBID_TAGS: ['style']});
|
||||
|
||||
// leave all safe HTML as it is and add style attributes to block-list
|
||||
var clean = DOMPurify.sanitize(dirty, {FORBID_ATTR: ['style']});
|
||||
|
||||
// extend the existing array of allowed tags and add <my-tag> to allow-list
|
||||
var clean = DOMPurify.sanitize(dirty, {ADD_TAGS: ['my-tag']});
|
||||
|
||||
// extend the existing array of allowed attributes and add my-attr to allow-list
|
||||
var clean = DOMPurify.sanitize(dirty, {ADD_ATTR: ['my-attr']});
|
||||
|
||||
// prohibit ARIA attributes, leave other safe HTML as is (default is true)
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOW_ARIA_ATTR: false});
|
||||
|
||||
// prohibit HTML5 data attributes, leave other safe HTML as is (default is true)
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOW_DATA_ATTR: false});
|
||||
|
||||
/**
|
||||
* Control behavior relating to Custom Elements
|
||||
*/
|
||||
|
||||
// DOMPurify allows to define rules for Custom Elements. When using the CUSTOM_ELEMENT_HANDLING
|
||||
// literal, it is possible to define exactly what elements you wish to allow (by default, none are allowed).
|
||||
//
|
||||
// The same goes for their attributes. By default, the built-in or configured allow.list is used.
|
||||
//
|
||||
// You can use a RegExp literal to specify what is allowed or a predicate, examples for both can be seen below.
|
||||
// The default values are very restrictive to prevent accidental XSS bypasses. Handle with great care!
|
||||
|
||||
|
||||
var clean = DOMPurify.sanitize(
|
||||
'<foo-bar baz="foobar" forbidden="true"></foo-bar><div is="foo-baz"></div>',
|
||||
{
|
||||
CUSTOM_ELEMENT_HANDLING: {
|
||||
tagNameCheck: null, // no custom elements are allowed
|
||||
attributeNameCheck: null, // default / standard attribute allow-list is used
|
||||
allowCustomizedBuiltInElements: false, // no customized built-ins allowed
|
||||
},
|
||||
}
|
||||
); // <div is=""></div>
|
||||
|
||||
var clean = DOMPurify.sanitize(
|
||||
'<foo-bar baz="foobar" forbidden="true"></foo-bar><div is="foo-baz"></div>',
|
||||
{
|
||||
CUSTOM_ELEMENT_HANDLING: {
|
||||
tagNameCheck: /^foo-/, // allow all tags starting with "foo-"
|
||||
attributeNameCheck: /baz/, // allow all attributes containing "baz"
|
||||
allowCustomizedBuiltInElements: false, // customized built-ins are allowed
|
||||
},
|
||||
}
|
||||
); // <foo-bar baz="foobar"></foo-bar><div is=""></div>
|
||||
|
||||
var clean = DOMPurify.sanitize(
|
||||
'<foo-bar baz="foobar" forbidden="true"></foo-bar><div is="foo-baz"></div>',
|
||||
{
|
||||
CUSTOM_ELEMENT_HANDLING: {
|
||||
tagNameCheck: (tagName) => tagName.match(/^foo-/), // allow all tags starting with "foo-"
|
||||
attributeNameCheck: (attr) => attr.match(/baz/), // allow all containing "baz"
|
||||
allowCustomizedBuiltInElements: true, // allow customized built-ins
|
||||
},
|
||||
}
|
||||
); // <foo-bar baz="foobar"></foo-bar><div is="foo-baz"></div>
|
||||
|
||||
/**
|
||||
* Control behavior relating to URI values
|
||||
*/
|
||||
// extend the existing array of elements that can use Data URIs
|
||||
var clean = DOMPurify.sanitize(dirty, {ADD_DATA_URI_TAGS: ['a', 'area']});
|
||||
|
||||
// extend the existing array of elements that are safe for URI-like values (be careful, XSS risk)
|
||||
var clean = DOMPurify.sanitize(dirty, {ADD_URI_SAFE_ATTR: ['my-attr']});
|
||||
|
||||
/**
|
||||
* Control permitted attribute values
|
||||
*/
|
||||
// allow external protocol handlers in URL attributes (default is false, be careful, XSS risk)
|
||||
// by default only http, https, ftp, ftps, tel, mailto, callto, cid and xmpp are allowed.
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOW_UNKNOWN_PROTOCOLS: true});
|
||||
|
||||
// allow specific protocols handlers in URL attributes via regex (default is false, be careful, XSS risk)
|
||||
// by default only http, https, ftp, ftps, tel, mailto, callto, cid and xmpp are allowed.
|
||||
// Default RegExp: /^(?:(?:(?:f|ht)tps?|mailto|tel|callto|cid|xmpp):|[^a-z]|[a-z+.\-]+(?:[^a-z+.\-:]|$))/i;
|
||||
var clean = DOMPurify.sanitize(dirty, {ALLOWED_URI_REGEXP: /^(?:(?:(?:f|ht)tps?|mailto|tel|callto|cid|xmpp|xxx):|[^a-z]|[a-z+.\-]+(?:[^a-z+.\-:]|$))/i;});
|
||||
|
||||
/**
|
||||
* Influence the return-type
|
||||
*/
|
||||
// return a DOM HTMLBodyElement instead of an HTML string (default is false)
|
||||
var clean = DOMPurify.sanitize(dirty, {RETURN_DOM: true});
|
||||
|
||||
// return a DOM DocumentFragment instead of an HTML string (default is false)
|
||||
var clean = DOMPurify.sanitize(dirty, {RETURN_DOM_FRAGMENT: true});
|
||||
|
||||
// use the RETURN_TRUSTED_TYPE flag to turn on Trusted Types support if available
|
||||
var clean = DOMPurify.sanitize(dirty, {RETURN_TRUSTED_TYPE: true}); // will return a TrustedHTML object instead of a string if possible
|
||||
|
||||
/**
|
||||
* Influence how we sanitize
|
||||
*/
|
||||
// return entire document including <html> tags (default is false)
|
||||
var clean = DOMPurify.sanitize(dirty, {WHOLE_DOCUMENT: true});
|
||||
|
||||
// disable DOM Clobbering protection on output (default is true, handle with care, minor XSS risks here)
|
||||
var clean = DOMPurify.sanitize(dirty, {SANITIZE_DOM: false});
|
||||
|
||||
// enforce strict DOM Clobbering protection via namespace isolation (default is false)
|
||||
// when enabled, isolates the namespace of named properties (i.e., `id` and `name` attributes)
|
||||
// from JS variables by prefixing them with the string `user-content-`
|
||||
var clean = DOMPurify.sanitize(dirty, {SANITIZE_NAMED_PROPS: true});
|
||||
|
||||
// keep an element's content when the element is removed (default is true)
|
||||
var clean = DOMPurify.sanitize(dirty, {KEEP_CONTENT: false});
|
||||
|
||||
// glue elements like style, script or others to document.body and prevent unintuitive browser behavior in several edge-cases (default is false)
|
||||
var clean = DOMPurify.sanitize(dirty, {FORCE_BODY: true});
|
||||
|
||||
// remove all <a> elements under <p> elements that are removed
|
||||
var clean = DOMPurify.sanitize(dirty, {FORBID_CONTENTS: ['a'], FORBID_TAGS: ['p']});
|
||||
|
||||
// change the parser type so sanitized data is treated as XML and not as HTML, which is the default
|
||||
var clean = DOMPurify.sanitize(dirty, {PARSER_MEDIA_TYPE: 'application/xhtml+xml'});
|
||||
|
||||
/**
|
||||
* Influence where we sanitize
|
||||
*/
|
||||
// use the IN_PLACE mode to sanitize a node "in place", which is much faster depending on how you use DOMPurify
|
||||
var dirty = document.createElement('a');
|
||||
dirty.setAttribute('href', 'javascript:alert(1)');
|
||||
var clean = DOMPurify.sanitize(dirty, {IN_PLACE: true}); // see https://github.com/cure53/DOMPurify/issues/288 for more info
|
||||
```
|
||||
|
||||
There is even [more examples here](https://github.com/cure53/DOMPurify/tree/main/demos#what-is-this), showing how you can run, customize and configure DOMPurify to fit your needs.
|
||||
|
||||
## Persistent Configuration
|
||||
|
||||
Instead of repeatedly passing the same configuration to `DOMPurify.sanitize`, you can use the `DOMPurify.setConfig` method. Your configuration will persist until your next call to `DOMPurify.setConfig`, or until you invoke `DOMPurify.clearConfig` to reset it. Remember that there is only one active configuration, which means once it is set, all extra configuration parameters passed to `DOMPurify.sanitize` are ignored.
|
||||
|
||||
## Hooks
|
||||
|
||||
DOMPurify allows you to augment its functionality by attaching one or more functions with the `DOMPurify.addHook` method to one of the following hooks:
|
||||
|
||||
- `beforeSanitizeElements`
|
||||
- `uponSanitizeElement` (No 's' - called for every element)
|
||||
- `afterSanitizeElements`
|
||||
- `beforeSanitizeAttributes`
|
||||
- `uponSanitizeAttribute`
|
||||
- `afterSanitizeAttributes`
|
||||
- `beforeSanitizeShadowDOM`
|
||||
- `uponSanitizeShadowNode`
|
||||
- `afterSanitizeShadowDOM`
|
||||
|
||||
It passes the currently processed DOM node, when needed a literal with verified node and attribute data and the DOMPurify configuration to the callback. Check out the [MentalJS hook demo](https://github.com/cure53/DOMPurify/blob/main/demos/hooks-mentaljs-demo.html) to see how the API can be used nicely.
|
||||
|
||||
_Example_:
|
||||
|
||||
```js
|
||||
DOMPurify.addHook(
|
||||
'beforeSanitizeElements',
|
||||
function (currentNode, hookEvent, config) {
|
||||
// Do something with the current node and return it
|
||||
// You can also mutate hookEvent (i.e. set hookEvent.forceKeepAttr = true)
|
||||
return currentNode;
|
||||
}
|
||||
);
|
||||
```
|
||||
|
||||
## Continuous Integration
|
||||
|
||||
We are currently using Github Actions in combination with BrowserStack. This gives us the possibility to confirm for each and every commit that all is going according to plan in all supported browsers. Check out the build logs here: https://github.com/cure53/DOMPurify/actions
|
||||
|
||||
You can further run local tests by executing `npm test`. The tests work fine with Node.js v0.6.2 and jsdom@8.5.0.
|
||||
|
||||
All relevant commits will be signed with the key `0x24BB6BF4` for additional security (since 8th of April 2016).
|
||||
|
||||
### Development and contributing
|
||||
|
||||
#### Installation (`npm i`)
|
||||
|
||||
We support `npm` officially. GitHub Actions workflow is configured to install dependencies using `npm`. When using deprecated version of `npm` we can not fully ensure the versions of installed dependencies which might lead to unanticipated problems.
|
||||
|
||||
#### Scripts
|
||||
|
||||
We rely on npm run-scripts for integrating with our tooling infrastructure. We use ESLint as a pre-commit hook to ensure code consistency. Moreover, to ease formatting we use [prettier](https://github.com/prettier/prettier) while building the `/dist` assets happens through `rollup`.
|
||||
|
||||
These are our npm scripts:
|
||||
|
||||
- `npm run dev` to start building while watching sources for changes
|
||||
- `npm run test` to run our test suite via jsdom and karma
|
||||
- `test:jsdom` to only run tests through jsdom
|
||||
- `test:karma` to only run tests through karma
|
||||
- `npm run lint` to lint the sources using ESLint (via xo)
|
||||
- `npm run format` to format our sources using prettier to ease to pass ESLint
|
||||
- `npm run build` to build our distribution assets minified and unminified as a UMD module
|
||||
- `npm run build:umd` to only build an unminified UMD module
|
||||
- `npm run build:umd:min` to only build a minified UMD module
|
||||
|
||||
Note: all run scripts triggered via `npm run <script>`.
|
||||
|
||||
There are more npm scripts but they are mainly to integrate with CI or are meant to be "private" for instance to amend build distribution files with every commit.
|
||||
|
||||
## Security Mailing List
|
||||
|
||||
We maintain a mailing list that notifies whenever a security-critical release of DOMPurify was published. This means, if someone found a bypass and we fixed it with a release (which always happens when a bypass was found) a mail will go out to that list. This usually happens within minutes or few hours after learning about a bypass. The list can be subscribed to here:
|
||||
|
||||
[https://lists.ruhr-uni-bochum.de/mailman/listinfo/dompurify-security](https://lists.ruhr-uni-bochum.de/mailman/listinfo/dompurify-security)
|
||||
|
||||
Feature releases will not be announced to this list.
|
||||
|
||||
## Who contributed?
|
||||
|
||||
Many people helped and help DOMPurify become what it is and need to be acknowledged here!
|
||||
|
||||
[JGraph 💸](https://github.com/jgraph), [GitHub 💸](https://github.com/github), [CynegeticIO 💸](https://github.com/CynegeticIO), [Sentry 💸](https://github.com/getsentry), [jarrodldavis 💸](https://github.com/jarrodldavis), [GrantGryczan](https://github.com/GrantGryczan), [Lowdefy 💸](https://twitter.com/lowdefy), [granlem ](https://twitter.com/MaximeVeit), [oreoshake ](https://github.com/oreoshake), [dcramer 💸](https://github.com/dcramer),[tdeekens ❤️](https://github.com/tdeekens), [peernohell ❤️](https://github.com/peernohell), [is2ei](https://github.com/is2ei), [SoheilKhodayari](https://github.com/SoheilKhodayari), [franktopel](https://github.com/franktopel), [NateScarlet](https://github.com/NateScarlet), [neilj](https://github.com/neilj), [fhemberger](https://github.com/fhemberger), [Joris-van-der-Wel](https://github.com/Joris-van-der-Wel), [ydaniv](https://github.com/ydaniv), [terjanq](https://twitter.com/terjanq), [filedescriptor](https://github.com/filedescriptor), [ConradIrwin](https://github.com/ConradIrwin), [gibson042](https://github.com/gibson042), [choumx](https://github.com/choumx), [0xSobky](https://github.com/0xSobky), [styfle](https://github.com/styfle), [koto](https://github.com/koto), [tlau88](https://github.com/tlau88), [strugee](https://github.com/strugee), [oparoz](https://github.com/oparoz), [mathiasbynens](https://github.com/mathiasbynens), [edg2s](https://github.com/edg2s), [dnkolegov](https://github.com/dnkolegov), [dhardtke](https://github.com/dhardtke), [wirehead](https://github.com/wirehead), [thorn0](https://github.com/thorn0), [styu](https://github.com/styu), [mozfreddyb](https://github.com/mozfreddyb), [mikesamuel](https://github.com/mikesamuel), [jorangreef](https://github.com/jorangreef), [jimmyhchan](https://github.com/jimmyhchan), [jameydeorio](https://github.com/jameydeorio), [jameskraus](https://github.com/jameskraus), [hyderali](https://github.com/hyderali), [hansottowirtz](https://github.com/hansottowirtz), [hackvertor](https://github.com/hackvertor), [freddyb](https://github.com/freddyb), [flavorjones](https://github.com/flavorjones), [djfarrelly](https://github.com/djfarrelly), [devd](https://github.com/devd), [camerondunford](https://github.com/camerondunford), [buu700](https://github.com/buu700), [buildog](https://github.com/buildog), [alabiaga](https://github.com/alabiaga), [Vector919](https://github.com/Vector919), [Robbert](https://github.com/Robbert), [GreLI](https://github.com/GreLI), [FuzzySockets](https://github.com/FuzzySockets), [ArtemBernatskyy](https://github.com/ArtemBernatskyy), [@garethheyes](https://twitter.com/garethheyes), [@shafigullin](https://twitter.com/shafigullin), [@mmrupp](https://twitter.com/mmrupp), [@irsdl](https://twitter.com/irsdl),[ShikariSenpai](https://github.com/ShikariSenpai), [ansjdnakjdnajkd](https://github.com/ansjdnakjdnajkd), [@asutherland](https://twitter.com/asutherland), [@mathias](https://twitter.com/mathias), [@cgvwzq](https://twitter.com/cgvwzq), [@robbertatwork](https://twitter.com/robbertatwork), [@giutro](https://twitter.com/giutro), [@CmdEngineer\_](https://twitter.com/CmdEngineer_), [@avr4mit](https://twitter.com/avr4mit) and especially [@securitymb ❤️](https://twitter.com/securitymb) & [@masatokinugawa ❤️](https://twitter.com/masatokinugawa)
|
||||
|
||||
## Testing powered by
|
||||
|
||||
<a target="_blank" href="https://www.browserstack.com/"><img width="200" src="https://www.browserstack.com/images/layout/browserstack-logo-600x315.png"></a><br>
|
||||
|
||||
And last but not least, thanks to [BrowserStack Open-Source Program](https://www.browserstack.com/open-source) for supporting this project with their services for free and delivering excellent, dedicated and very professional support on top of that.
|
||||
1692
node_modules/dompurify/dist/purify.cjs.js
generated
vendored
Normal file
1692
node_modules/dompurify/dist/purify.cjs.js
generated
vendored
Normal file
File diff suppressed because it is too large
Load Diff
1
node_modules/dompurify/dist/purify.cjs.js.map
generated
vendored
Normal file
1
node_modules/dompurify/dist/purify.cjs.js.map
generated
vendored
Normal file
File diff suppressed because one or more lines are too long
1690
node_modules/dompurify/dist/purify.es.js
generated
vendored
Normal file
1690
node_modules/dompurify/dist/purify.es.js
generated
vendored
Normal file
File diff suppressed because it is too large
Load Diff
1
node_modules/dompurify/dist/purify.es.js.map
generated
vendored
Normal file
1
node_modules/dompurify/dist/purify.es.js.map
generated
vendored
Normal file
File diff suppressed because one or more lines are too long
1698
node_modules/dompurify/dist/purify.js
generated
vendored
Normal file
1698
node_modules/dompurify/dist/purify.js
generated
vendored
Normal file
File diff suppressed because it is too large
Load Diff
1
node_modules/dompurify/dist/purify.js.map
generated
vendored
Normal file
1
node_modules/dompurify/dist/purify.js.map
generated
vendored
Normal file
File diff suppressed because one or more lines are too long
3
node_modules/dompurify/dist/purify.min.js
generated
vendored
Normal file
3
node_modules/dompurify/dist/purify.min.js
generated
vendored
Normal file
File diff suppressed because one or more lines are too long
1
node_modules/dompurify/dist/purify.min.js.map
generated
vendored
Normal file
1
node_modules/dompurify/dist/purify.min.js.map
generated
vendored
Normal file
File diff suppressed because one or more lines are too long
128
node_modules/dompurify/package.json
generated
vendored
Normal file
128
node_modules/dompurify/package.json
generated
vendored
Normal file
@@ -0,0 +1,128 @@
|
||||
{
|
||||
"scripts": {
|
||||
"lint": "xo src/*.js",
|
||||
"format": "npm run format:js && npm run format:md",
|
||||
"format:md": "prettier --write --parser markdown '**/*.md'",
|
||||
"format:js": "prettier --write '{src,demos,scripts,test,website}/*.js'",
|
||||
"commit-amend-build": "scripts/commit-amend-build.sh",
|
||||
"prebuild": "rimraf dist/**",
|
||||
"dev": "cross-env NODE_ENV=development BABEL_ENV=rollup rollup -w -c -o dist/purify.js",
|
||||
"build": "cross-env run-p build:umd build:umd:min build:es build:cjs",
|
||||
"build:umd": "cross-env NODE_ENV=development BABEL_ENV=rollup rollup -c -f umd -o dist/purify.js",
|
||||
"build:umd:min": "cross-env NODE_ENV=production BABEL_ENV=rollup rollup -c -f umd -o dist/purify.min.js",
|
||||
"build:es": "cross-env NODE_ENV=development BABEL_ENV=rollup rollup -c -f es -o dist/purify.es.js",
|
||||
"build:cjs": "cross-env NODE_ENV=development BABEL_ENV=rollup rollup -c -f cjs -o dist/purify.cjs.js",
|
||||
"test:jsdom": "cross-env NODE_ENV=test BABEL_ENV=rollup node test/jsdom-node-runner --dot",
|
||||
"test:karma": "cross-env NODE_ENV=test BABEL_ENV=rollup karma start test/karma.conf.js --log-level warn ",
|
||||
"test:ci": "cross-env NODE_ENV=test BABEL_ENV=rollup npm run test:jsdom && npm run test:karma -- --log-level error --reporters dots --single-run --shouldTestOnBrowserStack=\"${TEST_BROWSERSTACK}\" --shouldProbeOnly=\"${TEST_PROBE_ONLY}\"",
|
||||
"test": "cross-env NODE_ENV=test BABEL_ENV=rollup npm run lint && npm run test:jsdom && npm run test:karma -- --browsers Chrome"
|
||||
},
|
||||
"main": "dist/purify.cjs.js",
|
||||
"module": "dist/purify.es.js",
|
||||
"browser": "dist/purify.js",
|
||||
"files": [
|
||||
"dist"
|
||||
],
|
||||
"pre-commit": [
|
||||
"lint",
|
||||
"build",
|
||||
"commit-amend-build"
|
||||
],
|
||||
"xo": {
|
||||
"semicolon": true,
|
||||
"space": 2,
|
||||
"extends": [
|
||||
"prettier"
|
||||
],
|
||||
"plugins": [
|
||||
"prettier"
|
||||
],
|
||||
"rules": {
|
||||
"import/no-useless-path-segments": 0,
|
||||
"unicorn/prefer-optional-catch-binding": 0,
|
||||
"unicorn/prefer-node-remove": 0,
|
||||
"prettier/prettier": [
|
||||
"error",
|
||||
{
|
||||
"trailingComma": "es5",
|
||||
"singleQuote": true
|
||||
}
|
||||
],
|
||||
"camelcase": [
|
||||
"error",
|
||||
{
|
||||
"properties": "never"
|
||||
}
|
||||
]
|
||||
},
|
||||
"globals": [
|
||||
"window",
|
||||
"VERSION"
|
||||
]
|
||||
},
|
||||
"devDependencies": {
|
||||
"@babel/core": "^7.17.8",
|
||||
"@babel/preset-env": "^7.16.11",
|
||||
"@rollup/plugin-babel": "^5.3.1",
|
||||
"@rollup/plugin-commonjs": "^21.0.3",
|
||||
"@rollup/plugin-node-resolve": "^13.1.3",
|
||||
"@rollup/plugin-replace": "^4.0.0",
|
||||
"@types/dompurify": "^2.3.3",
|
||||
"@types/estree": "^1.0.0",
|
||||
"cross-env": "^7.0.3",
|
||||
"eslint-config-prettier": "^8.5.0",
|
||||
"eslint-plugin-prettier": "^4.0.0",
|
||||
"jquery": "^3.6.0",
|
||||
"jsdom": "^20.0.0",
|
||||
"karma": "^6.3.17",
|
||||
"karma-browserstack-launcher": "^1.5.1",
|
||||
"karma-chrome-launcher": "^3.1.0",
|
||||
"karma-firefox-launcher": "^2.1.2",
|
||||
"karma-qunit": "^4.1.2",
|
||||
"karma-rollup-preprocessor": "^7.0.8",
|
||||
"lodash.sample": "^4.2.1",
|
||||
"minimist": "^1.2.6",
|
||||
"npm-run-all": "^4.1.5",
|
||||
"pre-commit": "^1.2.2",
|
||||
"prettier": "^2.5.1",
|
||||
"qunit": "^2.4.1",
|
||||
"qunit-tap": "^1.5.0",
|
||||
"rimraf": "^3.0.2",
|
||||
"rollup": "^2.70.1",
|
||||
"rollup-plugin-includepaths": "^0.2.3",
|
||||
"rollup-plugin-terser": "^7.0.2",
|
||||
"xo": "^0.48.0"
|
||||
},
|
||||
"resolutions": {
|
||||
"natives": "1.1.6"
|
||||
},
|
||||
"name": "dompurify",
|
||||
"description": "DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. It's written in JavaScript and works in all modern browsers (Safari, Opera (15+), Internet Explorer (10+), Firefox and Chrome - as well as almost anything else using Blink or WebKit). DOMPurify is written by security people who have vast background in web attacks and XSS. Fear not.",
|
||||
"version": "2.4.1",
|
||||
"directories": {
|
||||
"test": "test"
|
||||
},
|
||||
"repository": {
|
||||
"type": "git",
|
||||
"url": "git://github.com/cure53/DOMPurify.git"
|
||||
},
|
||||
"keywords": [
|
||||
"dom",
|
||||
"xss",
|
||||
"html",
|
||||
"svg",
|
||||
"mathml",
|
||||
"security",
|
||||
"secure",
|
||||
"sanitizer",
|
||||
"sanitize",
|
||||
"filter",
|
||||
"purify"
|
||||
],
|
||||
"author": "Mario Heiderich <mario@cure53.de> (https://cure53.de/)",
|
||||
"license": "(MPL-2.0 OR Apache-2.0)",
|
||||
"bugs": {
|
||||
"url": "https://github.com/cure53/DOMPurify/issues"
|
||||
},
|
||||
"homepage": "https://github.com/cure53/DOMPurify"
|
||||
}
|
||||
Reference in New Issue
Block a user