remote/open-slopware
1
0
Fork 0
mirror of https://codeberg.org/small-hack/open-slopware.git synced 2026-08-28 17:04:05 +02:00
Code Issues Projects Releases Packages Wiki Activity

adding repo-slopscore as a tipp for automated scanning

Browse source 
If a project is not monitored by open-slopware, repo-slopscan can provide a quick overview if the repo contains traces of ai tools. This has sometimes false positives/negatives but can be used as a base to start further manual investigation and eventually.
This commit is contained in:
gebastel 2026-08-24 17:52:37 +02:00
commit 8f01f80ff5
1 changed files with 2 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -16,6 +16,8 @@ See a project on here that you love, and wish wasn't on here? Check out our [**N
Ready to fork a project to introduce a No AI policy? Check out our [**How to Slop Free Fork Guide**](./HOW_TO_SLOP_FREE_FORK.md).
If you quickly want to scan a git repo that isn't on this list, you could use [**Repo-Slopscore**](https://codeberg.org/polyphony/repo-slopscore) to do so. The tool checks if specific file exist in a repo or the git history/ignorefile contains specific strings. It does not scan the source code itself and could sometimes trigger false positives or false negatives. You can run it on your own computer or check out the [**public instance**](https://slopscan.ava.pet/) .
Any other questions? Please check out our [FAQ](./FAQ.md), and if your question isn't answered there, please feel free to start a [Discussion](https://codeberg.org/ethical-foss/open-slopware/issues/new?template=.forgejo%2fissue_template%2fdiscussion.yaml).
* [Definitions](#definitions)