highesttt/clanker-blocker — explained in plain English
Analysis updated 2026-05-18
Automatically block known bot or spam accounts from opening issues or pull requests.
Close and label submissions from blocklisted users while leaving a per-repository audit trail.
Combine multiple community blocklists in table, bullet, or one-per-line formats.
Pin an external blocklist to a specific commit hash to review changes before they take effect.
| highesttt/clanker-blocker | anomalroil/1key | danterolle/loqi | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Go | Go | Go |
| Last pushed | — | 2019-05-17 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 3/5 | 2/5 |
| Audience | ops devops | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
The daily account-block action needs a personal access token with block permissions since the default GitHub token cannot call that API.
clanker-blocker is a GitHub Action written in Go that automatically blocks users from interacting with your repositories based on community-curated blocklists. Its default list is a publicly maintained Markdown file tracking known bot and spam accounts. When a listed user tries to open an issue or pull request, the action can either block them at the account level or close their submission immediately with a comment and a label. The project provides two independent actions. The first runs on a daily schedule and calls GitHub's block API to apply account-level blocks for all users on the configured lists, preventing blocked accounts from opening issues, pull requests, or comments across every repository where you have admin rights. This requires a personal access token with block permissions, since the built-in GitHub token cannot call the block API. The second action triggers when a new issue or pull request is opened, checks whether the author appears on any configured list, and if so closes the submission with a comment and optionally applies a label named "blocklisted." This version needs no special token and creates a per-repository audit trail. You can extend beyond the default list by pointing to additional Markdown files. Three parsers handle different formats: a table with usernames in the first column, a bulleted list, or one username per line. The README recommends pinning any external list to a specific commit hash rather than a branch if you want to manually review changes before they take effect, since each sync inherits the list maintainer's judgment about who belongs on it.
A GitHub Action written in Go that blocks or closes issues and pull requests from users on community-curated bot and spam blocklists.
Mainly Go. The stack also includes Go, GitHub Actions, GitHub API.
License is not stated in the explanation.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.