github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-06-02 23:08:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #21683] EU AI Act Compliance: Risk Classification & Transparency for Multi-Model Support #122863

New Issue
Closed
opened 2026-05-21 01:55:55 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-21 01:55:55 -05:00
Owner
Copy Link

Originally created by @desiorac on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21683

Issue: EU AI Act Compliance Gap

Open WebUI supports multiple AI models (OpenAI, Anthropic, HuggingFace, local models) but lacks EU AI Act Article 6 compliance documentation.

Problem

Deployments in EU need formal documentation for:

  • Which models are high-risk (Art. 6)?
  • How user data is handled (GDPR + AI Act)?
  • Compliance checklist for deployments?

Proposed Solution

Add a COMPLIANCE.md with:

  1. Model Risk Matrix (per provider + architecture)
  2. Data Handling Policy (transparency for EU users)
  3. Compliance Checklist (admin deployment guide)

Example Checklist

High-Risk Models (Art. 6):
  [ ] Classify training data source
  [ ] Document data retention
  [ ] Add user notices

General-Purpose (lower risk):
  [ ] Document input/output handling

Why It Matters

  • Open WebUI is open-source + EU-friendly = opportunity for compliance leadership
  • Users need audit trail for high-risk deployments
  • Competitive advantage in EU market

Call to Action

Interested in:

  • Compliance framework design
  • Testing approach
  • Community contribution structure

Ref: EU AI Act Article 6 | ArkForge Compliance Scanner

Originally created by @desiorac on GitHub (Feb 21, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/21683 ## Issue: EU AI Act Compliance Gap Open WebUI supports multiple AI models (OpenAI, Anthropic, HuggingFace, local models) but lacks **EU AI Act Article 6** compliance documentation. ### Problem Deployments in EU need formal documentation for: - Which models are high-risk (Art. 6)? - How user data is handled (GDPR + AI Act)? - Compliance checklist for deployments? ### Proposed Solution Add a `COMPLIANCE.md` with: 1. **Model Risk Matrix** (per provider + architecture) 2. **Data Handling Policy** (transparency for EU users) 3. **Compliance Checklist** (admin deployment guide) ### Example Checklist ``` High-Risk Models (Art. 6): [ ] Classify training data source [ ] Document data retention [ ] Add user notices General-Purpose (lower risk): [ ] Document input/output handling ``` ### Why It Matters - Open WebUI is open-source + EU-friendly = opportunity for compliance leadership - Users need audit trail for high-risk deployments - Competitive advantage in EU market ### Call to Action Interested in: - Compliance framework design - Testing approach - Community contribution structure --- **Ref**: EU AI Act Article 6 | ArkForge Compliance Scanner
GiteaMirror commented 2026-05-21 01:55:56 -05:00
Author
Owner
Copy Link

@pr-validator-bot commented on GitHub (Feb 21, 2026):

⚠️ Missing Issue Title Prefix

@desiorac, your issue title is missing a prefix (e.g., bug:, feat:, docs:).

Please update your issue title to include one of the following prefixes:

  • bug: Bug report or error you've encountered
  • feat: Feature request or enhancement suggestion
  • docs: Documentation issue or improvement request
  • question: Question about usage or functionality
  • help: Request for help or support

Example: bug: Login fails when using special characters in password

<!-- gh-comment-id:3938042517 --> @pr-validator-bot commented on GitHub (Feb 21, 2026): # ⚠️ Missing Issue Title Prefix @desiorac, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`). Please update your issue title to include one of the following prefixes: - **bug**: Bug report or error you've encountered - **feat**: Feature request or enhancement suggestion - **docs**: Documentation issue or improvement request - **question**: Question about usage or functionality - **help**: Request for help or support Example: `bug: Login fails when using special characters in password`
GiteaMirror commented 2026-05-21 01:55:56 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Feb 21, 2026):

You need to read up on the EU AI Act. It seems you have multiple misconceptions about some things.

Also what's the compliance.md gonna do about it? That's not required anywhere.

Open a discussion not an issue, search for duplicates (which evidently you also didn't do) and please follow our issue templates if you open an issue. It exists for a reason

<!-- gh-comment-id:3938561513 --> @Classic298 commented on GitHub (Feb 21, 2026): You need to read up on the EU AI Act. It seems you have multiple misconceptions about some things. Also what's the compliance.md gonna do about it? That's not required anywhere. Open a discussion not an issue, search for duplicates (which evidently you also didn't do) and please follow our issue templates if you open an issue. It exists for a reason
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#122863
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?