[GH-ISSUE #13] Trusted Approval Process #9

New issue

Closed

opened 2026-10-18 14:01:37 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 14:01:37 +00:00

Owner

Originally created by @adamoutler on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/open-webui/community-platform/issues/13

"Official" functions should be hosted in a special repo by a designated maintainer like this one. The only reason you trust your instance is because you trust your admin. Whomever takes this role would need to be trustworthy because they'd be the admin for basically everyone.

Nobody wants to audit code, they just want features.
Many users can't read python, but they want features.
In the event a developer account is compromised, a malicious function update could exfiltrate all data on the platform.
In the event an untrustworthy party uploads malicious code, there should be a way to revoke it.

I suggest:

Trusted approver(s) who are known by the community.
A report/kill switch for items which are discovered to be malicious, or if a library/endpoints utilized is discovered to be malicious. Even if the plugin itself is fine, the container, libraries, other functions/tools, the LLM and/or APIs are part of the supply chain. The code provided as a part of an approved function should be disableable.
A rating/versioning system. While plugins work on one version, they may need work to run on a different version. If users are giving a thumbs up to the plugin on a specific version of OpenWebUI, it probably works and should be documented or suggested for use on that version.

It's real important this feature is implemented properly so Open WebUI doesn't end up on the news.

Originally created by @adamoutler on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/open-webui/community-platform/issues/13 "Official" functions should be hosted in a special repo by a designated maintainer like this one. The only reason you trust your instance is because you trust your admin. Whomever takes this role would need to be trustworthy because they'd be the admin for basically everyone. 1. Nobody wants to audit code, they just want features. 2. Many users can't read python, but they want features. 3. In the event a developer account is compromised, a malicious function update could exfiltrate all data on the platform. 4. In the event an untrustworthy party uploads malicious code, there should be a way to revoke it. I suggest: 1. Trusted approver(s) who are known by the community. 2. A report/kill switch for items which are discovered to be malicious, or if a library/endpoints utilized is discovered to be malicious. Even if the plugin itself is fine, the container, libraries, other functions/tools, the LLM and/or APIs are part of the supply chain. The code provided as a part of an approved function should be disableable. 3. A rating/versioning system. While plugins work on one version, they may need work to run on a different version. If users are giving a thumbs up to the plugin on a specific version of OpenWebUI, it probably works and should be documented or suggested for use on that version. It's real important this feature is implemented properly so Open WebUI doesn't end up on the news.

bsakaguchi closed this issue

2026-10-18 14:01:38 +00:00

bsakaguchi commented

2026-10-18 14:01:39 +00:00

Author

Owner

@tjbck commented on GitHub (Dec 7, 2025):

@tjbck commented on GitHub (Dec 7, 2025): #4

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

open-webui/community-platform#9

No description provided.

Rows
Columns