{"slug": "the-build-check-that-keeps-my-anonymous-site-anonymous", "title": "The build check that keeps my anonymous site anonymous", "summary": "An anonymous developer built a pre-build check for their Astro static site that scans every post against plain-text word lists and halts the build if a published post breaks a rule, keeping the live site unchanged while drafts are checked but cannot block builds. A second check runs before each commit to catch keys and IDs in every file, including private notes, so secrets never reach git history. The check, tested with 17 good and bad sample cases, failed twice in two days — once too strict over a harmless cost figure, and once too lenient when an outside AI reviewer found posts describing a service in enough combined detail to identify it despite every word passing.", "body_md": "I run this site under a pen name, so one careless line could tie it to the rest of my work. AI drafts my posts, which makes that line easier to miss. So I built a check that reads every post before the site is built, and stops the build if anything looks wrong.\n\nThe check is a small script that runs at the start of every build. If a published post breaks a rule, the build stops and the live site stays as it was. Drafts are still checked, but they cannot stop the build.\n\nA second, smaller check runs before each commit. It looks for keys and IDs in every file I commit, including my private notes. So a secret never reaches the git history, even in a private repository.\n\nThe site is a static site built with Astro. The code lives in a private GitHub repository, and Cloudflare builds and hosts it on each push.\n\n*From a draft to the live site. Two places can stop it.*\n\nThe main rules fall into five groups. The word lists are plain text files, so I can add to them without touching the code.\n\nThe check has its own tests: 17 cases built from good and bad sample files. Before I trust a change to the check, all 17 must pass.\n\nIt costs nothing extra. The check runs inside the normal build, and Cloudflare builds the site on its free plan. I have not measured how long the check itself takes.\n\nThe check failed me twice in two days. Once it was too strict, and once it was not strict enough.\n\nMy first post stopped the build over a cost figure. The number was harmless in that sentence. But the same number was on my banned list, for an unrelated reason.\n\nThe check does not know context. It only sees that a banned string is present.\n\nI reworded the number instead of loosening the check. I keep one rule for the list: adding terms is fine, removing or softening them is not. A false alarm costs me a minute. A missed leak cannot be undone.\n\nThe second problem was the opposite. I asked an outside AI to review the whole project. It pointed out that my posts described the LINE service in enough detail to find it, even though every single word passed the check.\n\nNo single term was the problem. The combination was.\n\n*How I describe the service now*\n\n**Before**\n\n**After**\n\nI updated the two posts that had the detailed description. The bugs, the fixes and the Make modules stayed in. Those are the useful part for readers.\n\nI would write the \"what may I say about this?\" line before the first post, not after. It is much easier to keep a description short from the start than to cut it back later.\n\nI would also accept that a word list is only half of the job. It catches names and keys well. It cannot see what several harmless details reveal together, so that needs a reader, human or AI, that looks at the whole post.\n\nLast checked: November 8, 2026. Astro static site on Cloudflare's free plan.\n\n*This article was drafted with AI assistance from my own build notes, and I checked it against what I actually built.*", "url": "https://wpnews.pro/news/the-build-check-that-keeps-my-anonymous-site-anonymous", "canonical_source": "https://dev.to/shikakeworks/the-build-check-that-keeps-my-anonymous-site-anonymous-33n9", "published_at": "2026-11-18 21:31:08+00:00", "updated_at": "2026-11-18 21:42:33.243814+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools"], "entities": ["Astro", "Cloudflare", "GitHub", "LINE"], "also_reported_by": [], "takeaway": "A word-list build gate catches names and keys but not what several individually harmless details reveal together, so pair it with a whole-post review by a human or AI and only ever add terms to the list, never soften them.", "recommendation": {"advice": "Run a word-list check at build time and a secret scan before each commit, but also review whole posts for combined-detail leaks, since no single banned term catches them.", "playbook": "output-verification", "playbook_url": "https://wpnews.pro/playbooks/output-verification"}, "alternates": {"html": "https://wpnews.pro/news/the-build-check-that-keeps-my-anonymous-site-anonymous", "markdown": "https://wpnews.pro/news/the-build-check-that-keeps-my-anonymous-site-anonymous.md", "text": "https://wpnews.pro/news/the-build-check-that-keeps-my-anonymous-site-anonymous.txt", "jsonld": "https://wpnews.pro/news/the-build-check-that-keeps-my-anonymous-site-anonymous.jsonld"}}