SlopStamp — Label & Govern AI Traces in Repos

Helps open-source maintainers detect, label, and policy-manage AI-generated commits and code

Problem

A developer wants to implement a feature in a FOSS project and finds virtually the same implementation, but the commit message says co-authored by an LLM and it was not upstreamed for unclear reasons—policy, neglect, or something else. Meanwhile the community debates what to call something that is not strictly open source but ships a feature-complete prompt. Maintainers lack a low-cost, consistent way to label and govern AI-generated contributions.

Solution

A local-first repo scanner and labeler: detects AI co-authorship traces, suspicious generation patterns, and LLM config files in git history, then produces customizable labels per commit/file. Maintainers can enforce an AI-participation declaration policy in PR checks and auto-generate contributor-facing policy templates, avoiding repeated manual explanations.

Users

Open-source maintainers, technical steering committees, engineering teams that need to audit code provenance

MVP

Scan local git history for AI co-author keywords and common generation markers; support custom regex and a project policy file; generate an exportable AI-participation report; provide a basic pre-commit/CI hook to block violations; output a contributor policy template

Revenue

Open-core plus team subscription (private-repo policy management, audit logs, multi-project dashboard); charge per repo or per seat

Why now

AI-generated code is flooding PRs, maintainer anxiety about provenance is real and new, and there is no de facto standard yet; a local tool requires no code hosting and is easy for an indie hacker to start