More granular language, tips, and making sure badge links work

This commit is contained in:
ethical-foss-admin 2026-06-20 16:56:01 +02:00
commit 81ff6da54b

View file

@ -217,7 +217,7 @@ Evidence may be, but is not limited to:
![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)
A policy, written or otherwise implied by maintainers' actions/statements, that permits the use of AI/LLMs in any capacity. Opening the door for people to vibecode counts as a "Permissive AI Policy".
A policy, written or otherwise implied by maintainers' actions/statements, that permits the use of AI/LLMs into the code base. Opening the door for others to use gen AI counts as a "Permissive AI Policy".
Evidence may be, but is not limited to:
@ -227,7 +227,9 @@ Evidence may be, but is not limited to:
- LLM code being merged into the default branch of a project's code repository. (Must be merged to count; Open PRs do not count)
> [!Important]
> If a core maintainer has noted that the code is entirely vibecoded, please use the ![Vibecoded](./badges/vibecoded.svg) instead. The vibecoded tag is specifically meant for *extreme* cases only.
> If a core maintainer has noted that the code is entirely vibecoded, please use the [![Vibecoded](./badges/vibecoded.svg)](#vibecoded) tag instead. The [![Vibecoded](./badges/vibecoded.svg)](#vibecoded) tag is specifically meant for *extreme* cases only.
If AI *code* is not permitted in the project, however a policy (written or otherwise) suggests that the maintainers condone the use of LLMs/AI to ingest the repo to "find bugs" or "better understand the repo", then you should not use this tag, and instead consider using the [![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)](#condones-llm-ingestion) tag.
## AI Functionality
@ -303,7 +305,7 @@ Evidence may be, but is not limited to:
![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)
Condones the use of AI/LLMs to ingest the project's contents. This can be for "understanding the code better", "finding bugs/security issues/optimizations". This tag is to be used independently for projects that generally reject the use of AI in their code repositories, issue trackers, and sponsorships, but still encourage or permit users to use LLMs to ingest their code base. This is independent of a project's licensing. This tag is to be used for the maintainers' statements about, or reactions to, the usage of LLMs/AIs to ingest the repo.
Condones the use of AI/LLMs to ingest the project's contents. This can be for "understanding the code better", "finding bugs/security issues/optimizations". This tag is to be used independently for projects that generally reject the use of AI in their code repositories, issue trackers, and sponsorships, but still encourage or permit users to use LLMs to ingest their code base. This is *independent of a project's licensing*. This tag is to be used for the maintainers' statements about, or reactions to, the usage of LLMs/AIs to ingest the repo.
The reason we still find this worthy of a tag is because it:
@ -316,7 +318,7 @@ Evidence may be, but is not limited to:
- Core maintainer using or accepting the use of AI for finding bugs or security issues
> [!tip]
> This tag is not to be confused with ![Permissive AI policy](./badges/permissive-ai-policy-orange.svg), which is for when there is already AI generated code in the codebase or an `AGENTS.md` in the repo.
> This tag is not to be confused with [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy), which is for when there is already AI generated code in the codebase or agent instructions, such as `AGENTS.md`, in the repo.
## Request for Help
@ -333,6 +335,9 @@ This is a special badge with a *positive* connotation. It certifies that a proje
> [!Note]
> Previous tainted status does not disqualify a project for this tag. Any project that was previously tainted, but took the steps for Removal (removed AI functionality, removed LLM agent instructions, and put out a No AI policy), can have this badge.
> [!Tip]
> If a project has an Anti-AI policy, but doesn't fit as an alternative to anything we have listed as tainted, consider checking out one of our [sibling repos](#sibling-repos) that specializes in elevating slop-free/No AI software.
# Sibling Repos
This is a section for repos that are similar to this one either because they are also forks of the original upstream, or because they align with our goal of identifying and avoiding AI/LLM usage OR identifying/elevating projects that do NOT use AI/LLMs. These repos are not all maintained by the same people, but we may share some contributors and are generally kind FOSS neighbors. ✨