Canonical: https://botbento.com/usecases/track-reuploads-of-a-codebase-on-github/
Format: Markdown representation of the public HTML page.

# Track reuploads of a codebase on GitHub and draft takedown notices

[Operations](https://botbento.com/usecases/ops/) · Intermediate

Scan GitHub for repositories that reuse shipped code, then queue notices

A scheduled bot searches GitHub for repositories whose files or bundles closely resemble the owner's web app, separates genuine reuploads from unrelated projects, and builds a review queue. For each likely match it collects repository details and drafts a takedown notice, leaving filing and correspondence to the owner.

## Quick answers

**What does it do?** Scan GitHub for repositories that reuse shipped code, then queue notices. Result: Review queue with draft notices.

**What does it need?** Tools: GitHub, Browser, Docs, Email. Intermediate: some setup.

**How do I run it?** On a schedule: Morning GitHub scan. Copy the prompt below into a bot in BotBento.

## How it works

1. On a schedule: Morning GitHub scan
2. Then: Match code signatures and rank
3. Result: Review queue with draft notices

## Prompt to start with

```text
Each morning, search GitHub for repositories that appear to reuse the owner's code, using distinctive strings, file names and bundle signatures rather than product names. For each candidate, record the repository URL, owner, description and the matching evidence in a doc, then rank matches by confidence. Draft a takedown notice for high-confidence matches. Do not send emails, file notices or contact repository owners until the user approves.
```

## Tools it uses

GitHub, Browser, Docs, Email

## Works with

BotBento

## Tags

dmca, github, code-monitoring, takedowns, review-queue

## Source

[Tell HN: GitHub refuses to remove cracked copies of my software after a month](https://news.ycombinator.com/item?id=49982498) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Scan repositories for committed local settings secrets](https://botbento.com/usecases/scan-repositories-for-committed-local-settings-secrets/) — Find credential-bearing config files in source control before they spread
- [Tracking AI-assisted commits across repositories](https://botbento.com/usecases/tracking-ai-assisted-commits-across-repositories/) — Scan commit metadata, log tool signatures, and compile metrics on generated code
- [Draft documentation updates from pull requests and issues](https://botbento.com/usecases/automated-documentation-updates-from-github-changes/) — Draft documentation edits from merged PRs and diffs, awaiting writer approval
