chore: format

docs/SECURITY.md

@@ -32,11 +32,13 @@ We appreciate the community's interest in identifying potential vulnerabilities.
 
 > [!NOTE]
 > A PoC (Proof of Concept) is a **demonstration of exploitation of a vulnerability**. Your PoC must show:
+>
 > 1. What security boundary was crossed (Confidentiality, Integrity, Availability, Authenticity, Non-repudiation)
 > 2. How this vulnerability was abused
 > 3. What actions the attacker can now perform
 >
 > **Examples of valid PoCs:**
+>
 > - Step-by-step reproduction instructions with exact commands
 > - Complete exploit code with detailed execution instructions
 > - Screenshots/videos demonstrating the exploit (supplementary to written steps)
@@ -53,17 +55,16 @@ We appreciate the community's interest in identifying potential vulnerabilities.
 
 > [!NOTE]  
 > **Note**: If you believe you have found a security issue that
-> 1) affects default configurations **or**
-> 2) represents a genuine bypass of intended security controls **or**
-> 3) works only with non-default configurations **but the configuration in question is likely to be used by production deployments**
-> **then we absolutely want to hear about it.** This policy is intended to filter configuration issues and deployment problems, not to discourage legitimate security research.
+>
+> 1. affects default configurations **or**
+> 2. represents a genuine bypass of intended security controls **or**
+> 3. works only with non-default configurations **but the configuration in question is likely to be used by production deployments** > **then we absolutely want to hear about it.** This policy is intended to filter configuration issues and deployment problems, not to discourage legitimate security research.
 
 8. **Threat Model Understanding Required**: Reports must demonstrate understanding of Open WebUI's self-hosted, authenticated, role-based access control architecture. Comparing Open WebUI to services with fundamentally different security models without acknowledging the architectural differences may result in report rejection.
 
 9. **CVSS Scoring Accuracy:** If you include a CVSS score with your report, it must accurately reflect the vulnerability according to CVSS methodology. Common errors include 1) rating PR:N (None) when authentication is required, 2) scoring hypothetical attack chains instead of the actual vulnerability, or 3) inflating severity without evidence. **We will adjust inaccurate CVSS scores.** Intentionally inflated scores may result in report rejection.
 
-> [!WARNING]
-> **Using CVE Precedents:** If you cite other CVEs to support your report, ensure they are **genuinely comparable** in vulnerability type, threat model, and attack vector. Citing CVEs from different product categories, different vulnerability classes or different deployment models will lead us to suspect the use of AI in your report.
+> [!WARNING] > **Using CVE Precedents:** If you cite other CVEs to support your report, ensure they are **genuinely comparable** in vulnerability type, threat model, and attack vector. Citing CVEs from different product categories, different vulnerability classes or different deployment models will lead us to suspect the use of AI in your report.
 
 11. **Admin Actions Are Out of Scope:** Vulnerabilities that require an administrator to actively perform unsafe actions are **not considered valid vulnerabilities**. Admins have full system control and are expected to understand the security implications of their actions and configurations. This includes but is not limited to: adding malicious external servers (models, tools, webhooks), pasting untrusted code into Functions/Tools, or intentionally weakening security settings. **Reports requiring admin negligence or social engineering of admins may be rejected.**
 
@@ -71,10 +72,12 @@ We appreciate the community's interest in identifying potential vulnerabilities.
 
 > [!NOTE]
 > AI-aided vulnerability reports **will not be rejected by us by default.** But:
+>
 > - If we suspect you used AI (but you did not disclose it to us), we will be asking tough follow-up questions to validate your understanding of the reported vulnerability and Open WebUI itself.
 > - If we suspect you used AI (but you did not disclose it to us) **and** your report ends up being invalid/not a vulnerability/not reproducible, then you **may be banned** from reporting future vulnerabilities.
 >
 > This measure was necessary due to the extreme rise in clearly AI written vulnerability reports, where the vast majority of them
+>
 > - were not a vulnerability
 > - were faulty configurations rather than a real vulnerability
 > - did not provide a PoC
@@ -90,6 +93,7 @@ If you want to report a vulnerability and can meet the outlined requirements, [o
 ## Product Security And For Non-Vulnerability Security Concerns:
 
 If your concern does not meet the vulnerability requirements outlined above, such as:
+
 - Suggestions for better default configuration values
 - Security hardening recommendations
 - Deployment best practices guidance
@@ -99,6 +103,7 @@ If your concern does not meet the vulnerability requirements outlined above, suc
 - General security questions about production deployment
 
 **then use one of the following channels instead:**
+
 - **Documentation issues/improvement ideas:** Open an issue on our [Documentation Repository](https://github.com/open-webui/docs)
 - **Feature requests:** Create a discussion in [GitHub Discussions - Ideas](https://github.com/open-webui/open-webui/discussions/) to discuss with the community if this feature request is wanted by multiple people
 - **Configuration help:** Ask the community for help and guidance on our [Discord Server](https://discord.gg/5rJgQTnV4s) or on [Reddit](https://www.reddit.com/r/OpenWebUI/)

src/lib/components/admin/Settings/Documents.svelte

@@ -816,7 +816,9 @@
 							<div class="flex justify-between w-full mt-2">
 								<div class="self-center text-xs font-medium">
 									<Tooltip
-									content={$i18n.t('Advanced parameters for MinerU parsing (enable_ocr, enable_formula, enable_table, language, model_version, page_ranges)')} 
+										content={$i18n.t(
+											'Advanced parameters for MinerU parsing (enable_ocr, enable_formula, enable_table, language, model_version, page_ranges)'
+										)}
 										placement="top-start"
 									>
 										{$i18n.t('Parameters')}
@@ -824,7 +826,9 @@
 								</div>
 								<div class="">
 									<Textarea
-									value={typeof RAGConfig.MINERU_PARAMS === 'object' && RAGConfig.MINERU_PARAMS !== null && Object.keys(RAGConfig.MINERU_PARAMS).length > 0
+										value={typeof RAGConfig.MINERU_PARAMS === 'object' &&
+										RAGConfig.MINERU_PARAMS !== null &&
+										Object.keys(RAGConfig.MINERU_PARAMS).length > 0
 											? JSON.stringify(RAGConfig.MINERU_PARAMS, null, 2)
 											: ''}
 										on:input={(e) => {