-
Two security checkers missed curl piped into /bin/bash
Our systemd unit and Claude Code hooks checkers flagged
curl | bashbut not| /bin/bash,| sudo -E bashor| env bash. Both are fixed and tested. -
Every month had 31 days: six import checkers and a bank-statement converter
A bank-statement converter exported 02/30 as 2026-02-30, and five import checkers shared its day check. All now use the real calendar.
-
Four ways our calendar checker said yes when it should have said no
A red-team pass on our free .ics checker found four bugs: empty reminder durations, case-sensitive FREQ, unchecked DURATION and a repair that broke a line.
-
1:75 is not a duration, and 1,5 is not fifteen hours
A red-team run found two duration bugs in the client profitability analyzer, then the same H:MM bug in six more tools. All fixed, each with a test.
-
Paste git status into a checker and it may read a path git never printed
A red-team pass on the .gitignore Explainer found six ways pasted git output came back as the wrong path. The fixes are now tested against git itself.
-
A CI gate that passes when the host is down: three checkers that exited 0 on failure
A failed lookup made the subdomain takeover checker exit 0, and two sibling checkers did the same. The fix, and a lint that now tests 21 CLIs.
-
Paste a URL into a subdomain takeover checker and it says you're safe
The resolver answers NXDOMAIN for https://blog.example.com/, so the checker reported no CNAME and no risk. The fix and the tests that now guard it.
-
A 61-character tagline: sixteen seeded faults in the launch-kit and GitHub Action generators
Sixteen faults seeded into two distribution scripts, eight caught. The launch kit could also write a Product Hunt tagline one character over its limit.
-
A typo that counts nowhere: two tax tools, sixteen seeded faults, one silent under-count
Sixteen seeded faults in two tax tools, nine caught. A manual hunt found worse: a mistyped state code that dropped days without a word.
-
An empty id swallows webhooks: sixteen seeded faults in a relay and a post composer
Sixteen faults seeded into a webhook relay and a post composer, seven caught. The hunt found an empty event id made the relay drop new webhooks.
-
Red team: an export invoice from last December crashed the checker
Ten seeded faults in a new Mexican export-invoice checker: its tests caught 4. Reading the code found a crash on any CFDI dated before 18 Jan 2024.
-
Colombian pesos have cents: a CFDI checker that disagreed with ISO 4217
Our free CFDI 4.0 checker flagged ten errors on a correct invoice in Colombian pesos, because it asked the JavaScript runtime how many decimals a currency has.
-
A branch called __proto__: what a pull request's name could do to our stats page
Our stats page counted CI runs per branch in a plain object. A branch named __proto__ polluted Object.prototype; a workflow named constructor crashed it.
-
Ten searches that were two: a seed too large for floating point in the league scheduler
A red-team run on the league scheduler's carry-over search: 8 seeded faults, 5 caught, and a real bug where a big shuffle seed turned ten searches into two.
-
One fix, three walkers: the crash our privacy checks fixed once and kept twice
A Node test that makes and removes a temp directory can crash any other test walking the same tree. We fixed it in one checker in October and missed two.
-
The browser learned Japan's invoices this morning. The Python CLI didn't
E-invoice preflight's Python CLI still called PINT Japan and Oman addresses unknown after the browser was fixed. A parity test now catches the next one.
-
The year that starts on a Wednesday: two test blind spots and two silent typos in a residency day counter
Sixteen seeded bugs, three escaped. One hid because 2025 begins on a Wednesday. Two real parsing bugs let a state-code typo take days from the right state.
-
A fee table with a hole in it: red-teaming the UCR fee calculator, and 203 CSV exports that run formulas
Ten faults seeded into the UCR fee calculator, six caught. Also fixed: a gapped fee table gave a wrong price jump, and CSV export ran typed formulas.
-
Unit 1 is not in the unit column: twelve seeded faults in a new synthetic control tool
Twelve faults seeded into the synthetic control engine, four caught. A manual hunt found that numeric unit ids made the treated unit disappear.
-
7.000000000000001%: the rounding bug in 22 places, and a test that keeps it out
A Form 2210 penalty warning printed its rate as 7.000000000000001%. The same bug sat in 21 more places; one test now scans every page and script.
-
"6,000" is two numbers: how a VAT checker missed a trader over the threshold
Five calculators split pasted lists on commas, so 6,000 became 6 and 0, and a UK VAT checker told a trader over £90,000 they were below it. The fix and a lint.
-
The Details column is not the merchant: a bank-import fix in the expense tracker
A red-team pass on the free expense tracker: 16 seeded faults, 11 caught, all 16 caught after five new tests, and a bank-CSV column bug fixed.
-
165 lint errors on a clean main: running the linter version CI pins
Our local CI runner reported 165 ruff errors on code CI passes: a newer ruff sat first on PATH. It now runs pinned tools from a venv of the job's pip install.
-
The bug-seeding tool now runs the test command the audit file wrote down
quality_mutate.py crashed on the cd-prefixed test commands that audit files record. It now runs them through bash from the repository root.
-
The site's tests read every page twenty times
Twenty tests each re-read all 4,471 built pages. Reading each page once cut the tests after the build from 126 s to 58 s, with every test unchanged.
-
The slow test was a hidden second build
A per-test timing of our site builder's tests showed one test spending 31 s on a whole build. Moving it into a child process cut the suite from 204 s to 180 s.
-
Three tests went red on main and no CI job noticed
A new systemd checker shipped without its GitHub Action, Nix package or pre-commit hook. The tests that catch that ran in no pull request workflow.
-
It was tomorrow after 4 pm: 27 date tools that followed London's calendar
A sweep loaded 109 date tools in UTC, Los Angeles and Kiritimati. 27 defaulted to tomorrow's date for US users each evening, and one rounded a deadline wrong.
-
"United States" is not "US": how a holiday calendar got lost between a CRM export and the call queue
A prospect whose CRM row said "United States" got no holiday calendar, so the call queue left a call on Thanksgiving. Found by a red-team run.
-
0x64 is not an amount: four ways a number broke our e-invoice checker
A red-team pass on einvoice-preflight found that the web page read 0x64 as 100 and the CLI crashed on bad or huge amounts. One shared number rule fixed both.
-
A "for example" in the footer excused every fake-review claim on the page
A red-team run found five kinds of copy that slipped a fake-review claim past our honest-marketing check. It now catches all five.
-
Four ways a logger file could lie to a concrete strength estimate
A red-team run on the new concrete maturity calculator found four ordinary inputs that gave a wrong number with no error, and fixed all four.
-
Eleven ways past our mixed-content check, and why it now parses HTML
Our check for plain-http loads on https pages used a regex, so unquoted attributes, srcset, base href and CSS url() got past it. What such a lint must cover.
-
One line that said "Note:" cut a customer's reply in half
A red-team pass found that an unescaped 'From ...' paragraph followed by 'Note:' split a sales-agent reply and dropped half of it.
-
One full build fewer, and the tests finish no sooner
Our site tests built the same site three times. Removing one build cut CPU by 13% over three timed pairs. Wall time did not move, and here is why.
-
One usage counter, 1,293 copies: testing them all at once
A red-team run found our 1,293 copies of an on-device usage counter shared an untested gap. One contract now runs every copy; 263 copies were fixed.
-
1024 or 1099.5: a 7% BigQuery overcharge and a phthalate test our checklist skipped
A red-team run found a cost advisor that used GiB maths on GB input, and a safety-test checklist that left the EU phthalate test off adult clothing.
-
"constructor" is not a property type: one JavaScript lookup, four broken tools, 305 to watch
A plain object map finds Object.prototype for "constructor" or "toString". It broke four of our tools; a CI lint fails new ones and tracks 305 old.
-
Our report index caught 3 of 10 seeded bugs, then 10 of 10
We seeded 10 faults into doc_index.py, which tags agent reports. Its tests caught 3. New tests close the gaps, and the run fixed six real defects.
-
DynamicUser=yes, User=root: the service our checker said was not root
systemd prefers an existing static user over a dynamic one, and root always exists. Our unit-file checker missed it; the fix and a twin-parity test.
-
'Over 40 in.' when we had tried 60: three quiet faults in our duct sizer
A red-team run on our free duct sizer found a hard-coded size in a warning, a return trunk that vanished silently, and a JavaScript object-key trap.
-
"You can lose 126% of your dogs": a price-raise table in six calculators that went past 100%
Customers you can lose before a raise stops paying: extra / (contribution + extra). With negative margin it tops 100%, and six of our calculators showed that.
-
A consultant shown $400 instead of $5,000: the SSTB phase-in our QBI calculator skipped
In the phase-in range an SSTB's QBI is scaled, then the wage limit phases in. Our calculator skipped step two and put the $400 minimum in the wrong place.
-
'Back on the 31st', said in November: the dates our reply sorter invented
JavaScript's Date.UTC turns February 30 into March 2. Our reply sorter booked follow-ups on days nobody named, and one huge number could crash an inbox run.
-
Our security.txt checker pointed signed files at the wrong line
Red-teaming our RFC 9116 security.txt checker found 3 bugs: wrong line numbers in signed files, a leap second rejected, a quoted charset flagged.
-
The $400 floor: ten of our tax calculators charged self-employment tax on tiny profits
Ten of our tax calculators charged self-employment tax on profits under $433, or checked the $400 Schedule SE floor against the wrong number.
-
The optional first column: three parsers that read a label as data
A wall condensation check read a month number as the temperature, a fee tool read an order number as the price, a CAA checker read a parameter as a CA.
-
The year the tables run out: two fallbacks that disagreed with themselves
When a tax table lacks the year asked for, every lookup must fall back the same way. Two of ours did not, and a shared file's 16 copies drifted.
-
Thirteen date checks that said yes to 30 February
In V8, Date.parse('2026-02-30') is a real timestamp, 2 March. Thirteen of our validators trusted it to reject bad dates. A lint now flags the pattern.
-
Thirty-six usage counters, and none of their tests ever stored a null
A red-team run seeded 24 faults. Three of the five that escaped were one blind spot in a counter copied into 36 products. One shared check now covers all 36.