Last month I open-sourced awesome-crypto-cards — a curated list of 136 crypto debit and credit cards. This post is about the boring infrastructure: why I run awesome-lint in CI, how I keep the list synced with the dataset behind sweepbase.net, and where I underestimated effort.

Why a flat README, not a database

The list lives as a single README.md. No JSON, no YAML, no static site. People who land on a GitHub awesome-list expect to scan markdown, not click into an interactive viewer.

Trade-offs I accepted: no programmatic queries, no filtering UI, no auto-generated content.

Trade-offs I avoided: an extra build step, broken links from generator bugs, and the friction of "wait, where do I edit this?"

The awesome-lint CI

Every push runs awesome-lint via GitHub Actions.…