purifai 3.0.1 → 3.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/DISCLAIMER.md ADDED
@@ -0,0 +1,34 @@
1
+ # Purifai — security disclaimer
2
+
3
+ Moved verbatim out of `LICENSE`, where the appended text prevented GitHub
4
+ from detecting the MIT license. The MIT terms are unchanged and remain in
5
+ `LICENSE`; nothing below alters them.
6
+
7
+ ```
8
+ ADDITIONAL SECURITY DISCLAIMER:
9
+
10
+ WHILE THIS SOFTWARE HAS BEEN TESTED AGAINST KNOWN XSS ATTACK VECTORS, NO
11
+ SECURITY LIBRARY CAN GUARANTEE COMPLETE PROTECTION AGAINST ALL POSSIBLE
12
+ ATTACKS. NEW ATTACK VECTORS MAY BE DISCOVERED THAT COULD BYPASS CURRENT
13
+ PROTECTIONS.
14
+
15
+ THE AUTHORS AND CONTRIBUTORS SPECIFICALLY DISCLAIM ANY LIABILITY FOR:
16
+ - SECURITY BREACHES OR INCIDENTS
17
+ - DATA LOSS OR CORRUPTION
18
+ - FINANCIAL OR BUSINESS LOSSES
19
+ - ANY DAMAGES RESULTING FROM THE USE OF THIS SOFTWARE
20
+
21
+ USERS ARE RESPONSIBLE FOR:
22
+ - TESTING THE SOFTWARE IN THEIR SPECIFIC ENVIRONMENT
23
+ - IMPLEMENTING ADDITIONAL SECURITY MEASURES
24
+ - CONDUCTING THEIR OWN SECURITY ASSESSMENTS
25
+ - KEEPING THE SOFTWARE UPDATED
26
+
27
+ THIS SOFTWARE IS ONE COMPONENT OF A COMPREHENSIVE SECURITY STRATEGY AND
28
+ SHOULD BE USED IN CONJUNCTION WITH OTHER SECURITY BEST PRACTICES INCLUDING
29
+ BUT NOT LIMITED TO CONTENT SECURITY POLICY (CSP), INPUT VALIDATION, OUTPUT
30
+ ENCODING, AND DEFENSE-IN-DEPTH APPROACHES.
31
+
32
+ BY USING THIS SOFTWARE, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTOOD
33
+ THESE DISCLAIMERS AND AGREE TO USE THE SOFTWARE AT YOUR OWN RISK.
34
+ ```
package/LICENSE CHANGED
@@ -1,6 +1,6 @@
1
1
  MIT License
2
2
 
3
- Copyright (c) 2025 Purifai
3
+ Copyright (c) 2025 Mojtaba Beheshti
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining a copy
6
6
  of this software and associated documentation files (the "Software"), to deal
@@ -19,30 +19,3 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
19
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
20
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
21
  SOFTWARE.
22
-
23
- ADDITIONAL SECURITY DISCLAIMER:
24
-
25
- WHILE THIS SOFTWARE HAS BEEN TESTED AGAINST KNOWN XSS ATTACK VECTORS, NO
26
- SECURITY LIBRARY CAN GUARANTEE COMPLETE PROTECTION AGAINST ALL POSSIBLE
27
- ATTACKS. NEW ATTACK VECTORS MAY BE DISCOVERED THAT COULD BYPASS CURRENT
28
- PROTECTIONS.
29
-
30
- THE AUTHORS AND CONTRIBUTORS SPECIFICALLY DISCLAIM ANY LIABILITY FOR:
31
- - SECURITY BREACHES OR INCIDENTS
32
- - DATA LOSS OR CORRUPTION
33
- - FINANCIAL OR BUSINESS LOSSES
34
- - ANY DAMAGES RESULTING FROM THE USE OF THIS SOFTWARE
35
-
36
- USERS ARE RESPONSIBLE FOR:
37
- - TESTING THE SOFTWARE IN THEIR SPECIFIC ENVIRONMENT
38
- - IMPLEMENTING ADDITIONAL SECURITY MEASURES
39
- - CONDUCTING THEIR OWN SECURITY ASSESSMENTS
40
- - KEEPING THE SOFTWARE UPDATED
41
-
42
- THIS SOFTWARE IS ONE COMPONENT OF A COMPREHENSIVE SECURITY STRATEGY AND
43
- SHOULD BE USED IN CONJUNCTION WITH OTHER SECURITY BEST PRACTICES INCLUDING
44
- BUT NOT LIMITED TO CONTENT SECURITY POLICY (CSP), INPUT VALIDATION, OUTPUT
45
- ENCODING, AND DEFENSE-IN-DEPTH APPROACHES.
46
-
47
- BY USING THIS SOFTWARE, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTOOD
48
- THESE DISCLAIMERS AND AGREE TO USE THE SOFTWARE AT YOUR OWN RISK.
package/README.md CHANGED
@@ -10,6 +10,11 @@
10
10
 
11
11
  **Readable text from hostile HTML—without a DOM.**
12
12
 
13
+ [Live site](https://purifai.worksonmy.dev) ·
14
+ [npm](https://www.npmjs.com/package/purifai) ·
15
+ [Project notes](https://worksonmy.dev/projects/purifai) ·
16
+ [Issues](https://github.com/moji2002/purifai/issues)
17
+
13
18
  Purifai is a fixed-policy HTML-to-text converter for servers, browsers, and
14
19
  edge runtimes. It keeps useful document structure, drops non-reader bodies, and
15
20
  enforces input, output, nesting, and retained-token limits while scanning.