Slopfree Software Index

Atom feed RSS feed

A list of software that has taken steps to reject AI in its development processes.

There's been a lot of news about prominent open-source projects increasingly using LLMs. But this only shows one side of the story - we don't see all the software that rejects AI contributions and continues to be human-made.

This is not an exhaustive list! If you see a project that fits the criteria below, please raise an issue or a PR!

The List

Databases

Development

Gaming

Graphics

Hardware

Health

Internet

Languages

Libraries

Multimedia

Office

Operating Systems

Organizations

Programming

Scientific

Uncategorized

Utilities

Virtualisation

Retractions

Contributing

See CONTRIBUTING.md

Tips

Buy Me a Coffee at ko-fi.com Donate using Liberapay

Tips would be greatly appreciated; each tip will encourage me to continue building awesome software and help with living expenses! At the time of writing (2026-05-18), all tips go to the project maintainer brib.

Credits

Other Lists of Slopfree Software

Why care about slopfree software?

Software Reliability and Stability

AI is notorious for its ability to create subtle bugs and security issues that are hard to detect. In AWS, this even directly led to an outage.

The project maintainer brib has noticed that LLMs incentivise coders to think less critically about the resulting code. This has the potential to negatively impact the quality of the codebase and the psychological wellbeing of developers.

By choosing human software, you can be assured that the maintainers have a good understanding of the codebase and are able to reason about and fix any potential issues. This helps ensure the long-term reliability and stability of the software you are using.

Psychological Integrity

There is evidence to indicate that AI use harms reasoning ability and skill formation. For example:

By supporting human-made software, you can help developers maintain their skills and reasoning abilities.

Harm Reduction

By choosing human software, you can be assured that the developers are not funding machines that are fuelling the climate crisis and an unjustified war in the Middle East.

Copyright

By choosing human software, you can be assured that your business will not be adversely affected by copyright lawsuits that may affect the legality of the software you are using or your ability to protect your own intellectual property.

Effectiveness of Having a No-AI Policy

Every time a project considers adding a no-AI policy, someone invariably asks "Why bother making such a policy when AI-users can just lie?"

Almost all open source projects have rules that are impossible to enforce perfectly. For example, most open source projects have policies prohibiting illegal content. But most maintainers are not Supreme Court Justices, so they do not know for certain whether a piece of code is illegal. The best maintainers can do is try to enforce their policies as best they can with limited information, and with the understanding mistakes will sometimes happen.

It will likely always be possible for someone to carefully edit LLM-generated code to remove any traces of its origins, but that would take a lot of work. People who use LLMs typically aren't interested in doing a lot of work.

Finally, it is worth noting that the vast majority of people who contribute to open source projects do so in good faith. Most FOSS contributors are very passionate about the projects they work on, and they devote their free time to making free software better because they want to.

Hence, if a project has a clearly stated policy against LLM-generated contributions, most potential contributors will respect the policy.

Keep software slopfree!

There is currently a significant maintainability crisis in open-source software. In many cases, the adoption of LLMs is a response to this maintainability crisis. Please do not attack maintainers simply for using LLMs.

You can do your part to keep software slopfree!

License

This project is a combination of documentation and code and is therefore covered by two licenses.

All code is covered by GNU-GPL-3.0.

All documentation is covered by CC-BY-SA.

For clarification, individual files are labelled with the appropriate SPDX-License-Identifier in the comments.