# Choosing Linux App Stores That Reject AI-Generated Software

Why some Linux users are migrating to stricter repositories to avoid AI-generated code.

- **Source:** [How-To Geek](https://www.howtogeek.com)
- **Published:** 2026-10-28
- **Topic:** [Software & Engineering](https://brifing.si/c/engineering)
- **Original article:** <https://www.howtogeek.com/i-switched-from-flathub-to-a-linux-app-store-that-doesnt-allow-ai-slop/>
- **On Brifing:** https://brifing.si/s/1e1ba23d-7976-45fc-b3d6-1c87faa85941

## Flathub Reverses AI Ban

In May 2026, Flathub implemented a strict ban on AI-generated code and documentation to combat low-quality submissions. By October, the repository reversed this policy, shifting to a disclosure-based model. Developers must now declare AI usage, though reviewers retain discretion over acceptance, creating ambiguity regarding the enforcement of these new standards.

## The Disclosure Policy Limitations

Flathub's current policy requires disclosure of AI-generated material in packaging and code, but it does not guarantee that this information reaches end users. Because auditing proprietary or complex software for AI content is technically difficult, the burden falls on volunteer reviewers. This shift prompted users to seek more restrictive alternatives.

## AppCenter's Hardline Stance

elementary’s AppCenter maintains a strict prohibition against AI-generated content, including code, artwork, and documentation. Unlike Flathub, AppCenter does not rely on developer disclosure for judgment calls. Instead, it enforces a hard requirement checked through both automated systems and human review during the public pull request process on GitHub.

## Technical Integration Flexibility

AppCenter is not exclusive to elementary OS and can be added to any distribution supporting Flatpak via a simple command. Once added, its applications appear alongside Flathub apps in standard software centers like GNOME Software. This allows users to maintain access to both repositories while prioritizing AppCenter for specific, curated software needs.

## Strict Curation Trade-offs

The primary cost of using AppCenter is a significantly smaller catalog. The store mandates native GTK3 or GTK4 front ends, effectively excluding Electron, Qt, and Java applications. This restriction limits the availability of cross-platform tools and major productivity suites, making it a specialized choice rather than a complete replacement for Flathub.

## Managing Repository Priorities

Users are adopting a hybrid approach, keeping Flathub for large, established projects while using AppCenter as the primary source for small utilities. This strategy mitigates the risk of installing low-effort AI-generated tools. The challenge remains in identifying the source of an application, as software centers often obscure the specific remote repository used.

## Scalability of Curation Policies

Flathub’s massive scale makes strict bans difficult to enforce, necessitating the move toward disclosure. Conversely, AppCenter’s narrow focus on GTK-native apps keeps submission volumes manageable, allowing for consistent enforcement. Other organizations, such as GNOME Circle, have similarly paused submissions or adopted new policies to manage the influx of machine-generated software.

## The Future of Curation

While no repository can perfectly prevent dishonest developers from bypassing checks, policy-driven curation remains a vital tool for Linux users. By choosing where to source software, users exert pressure on maintainers to uphold quality standards. Ultimately, the shift highlights a growing demand for transparency and human-centric development in open-source software ecosystems.

## Sources covering this story

- https://www.howtogeek.com/i-switched-from-flathub-to-a-linux-app-store-that-doesnt-allow-ai-slop/ — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._