CyrisXD

Auto-block known spam bot accounts from your personal GitHub account and/or every org you admin. Pulls a community-maintained list and syncs your block lists on a schedule.

11
1
100% credibility
Found May 14, 2026 at 14 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Shell
AI Summary

GitHub Action that automatically blocks known spam bot accounts on personal accounts and administered organizations using a community-maintained list.

How It Works

1
🔍 Discover the Tool

You're annoyed by spam bots flooding your GitHub notifications and discover this handy helper to block them automatically.

2
📋 Make Your Own Copy

Click the fork button to create your personal version of the blocker right on GitHub.

3
🔒 Link Your Account Securely

Add a private permission from your GitHub settings so the tool can update your block lists safely.

4
⚙️ Turn On Automation

Head to the actions area, enable it, and choose if it covers just you or your teams too.

5
▶️ Run the First Update

Click to start the first sync and see it pull the latest spam list and apply blocks.

6
Let It Run on Schedule

Now it checks and updates your blocks every so often without you lifting a finger.

🛡️ Protected from Spam

Your GitHub account and any teams you lead stay clear of known troublemaker bots.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 14 to 11 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is block-clankers?

Block Clankers auto-blocks known spam bot accounts, called clankers, from your personal GitHub account and/or every org you admin. This Shell-based GitHub Action pulls a community-maintained list and syncs your block lists on a schedule, solving endless manual blocking of repeat offenders. Fork it, add a PAT secret with user and admin:org scopes, and target @me, @auto, or specific orgs.

Why is it gaining traction?

It diffs your current blocks against the source list for minimal API writes, with built-in throttling, retries, and rate-limit respect to stay under GitHub limits. Dry-run mode lets you preview changes, and unblock-removed cleans up lists if enabled. Devs dig the hands-off sync from a vetted community-maintained clankers.json, no more chasing bots across accounts.

Who should use this?

GitHub org admins tired of spam in PRs and issues across multiple orgs. Personal account owners blocking the same bot lists weekly. Teams managing public repos hit by known clankers wanting scheduled auto-block protection.

Verdict

Solid for low-effort spam defense, but at 11 stars and 1.0% credibility score, it's immature—great docs and API smarts, but test dry-run first and pin the source list. Fork if bots bug you.

(178 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.