Operations · Intermediate
Verified
Automated verification
- Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
- Drafted by deepseek-flash via DeepSeek API.
- Second-model review: kimi-code/k3.1-pro (no critical or high findings).
- Verified .
- Automated checks and AI review only, not human review.
Track reuploads of a codebase on GitHub and draft takedown notices
Scan GitHub for repositories that reuse shipped code, then queue notices
Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.
- On a scheduleMorning GitHub scan
- ThenMatch code signatures and rank
- ResultReview queue with draft 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.
Prompt to start with
BotBentoRecommended
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.