-
The Worksheet Said Michigan's Discount Was Applied. It Wasn't.
ai-bookkeeper took no state discount on tax lines not labelled '<ST> state', while its note said the discount was applied. Found by a red-team run.
-
--tz=-5 ran in UTC with no warning. Red-teaming the on-call load analyzer's CLI
Eight faults seeded into the on-call load analyzer CLI, two caught. Its --tz flag quietly reported nights in UTC; two sibling CLIs had the same silent default.
-
A result code that decoded to null, and a repeat penalty nothing tested. Red-teaming Quick Pick's team ranges
10 faults seeded into Quick Pick's rank engine, 5 caught. A result code of JSON null broke the team box, so 205 link decoders now get fuzzed on every PR.
-
A 0.5 m/s lift never reaches full acceleration. Red-teaming the elevator traffic tool
24 faults seeded into the elevator traffic tool, 18 caught. The flight-time formula was wrong for slow lifts that hit rated speed before full acceleration.
-
34 test suites no workflow ran, and the one that was red. Red-teaming the dev-log builder
8 faults seeded into platform/devlog, 4 caught. The suite ran in no workflow. Neither did 33 others, and one of those had been red on main since this morning.
-
The follow-up that would have sent the last nudge first
16 seeded faults, 8 uncaught, 6 real test gaps: a reference reminder that could open with the last nudge, and a CI gate whose exit code no test read.
-
30 February, spelled a third way. Red-teaming the on-call and delivery-commission analyzers
16 faults seeded into two analyzers, 8 caught. The on-call parser read 2026-02-30 as 2 March, in a spelling our date lint missed. A Mailchimp check had it too.
-
The repair button that broke valid invoices
einvoice-preflight's JSON repair rounded unit prices to cents and summed VAT per line, so it rewrote correct invoices into failing ones. The fix and the guard.
-
The safety check that stopped the page: typeof localStorage throws when cookies are blocked
21 of our tools opened with a line meant to make storage safe. With site data blocked, that line threw and stopped the whole tool before it started.
-
The sample file works, the real export crashes: Math.max(...rows) in five analyzers
Five of our CSV analyzers crashed on files of about 125,000 rows, all from one idiom: Math.max(...rows.map(f)). Fixed with loops; a lint stops new copies.
-
The trailing space that split a team survey: a red-team pass on Quick Pick's rank page
20 faults seeded into the new rank page, 6 caught. Hunting by hand found a real bug: a long option made every team code 'for a different list'.
-
The zeros a sprinkler solver was multiplying: four times faster, same digits
A sprinkler network's matrix is nearly banded, so most dense Cholesky products are zeros. Skipping them: 4.6x faster, byte-identical output.
-
Twelve Free Tools Read 30 February as 2 March. Now They Refuse It.
A lint for impossible dates missed the usual way to write the check. Widening it found 12 tools that moved 30 February into March, one a paycheck deadline.
-
When 12,50 was read as 1,250
33 CSV tools took the decimal format from the delimiter, so a tab-delimited European file read 12,50 as 1,250. They now read the amounts themselves.
-
Two million regex calls to find zero bugs: a lint nine times faster
A calendar-date lint ran six regexes on every line of 5,704 files. A fixed-text check every match must pass cut it from 3.5 s to 0.4 s, same output.
-
A cent our wash-sale checker made up, and the variable that was meant to stop it
Splitting a disallowed wash-sale loss over several buys could add a cent more to basis than was disallowed. The fix, and what 22 seeded faults showed.
-
A budget alert that missed by a third of a trillionth of a dollar: six boundary bugs our tests did not see
We seeded 24 faults into three products. The tests caught 18. All six escapes sat on a boundary, and one of them depends on floating-point sums.
-
An account number that looked like a 401(k)
The wash sale checker treated any account number containing 401 as a retirement account and dropped those sales without a word. Now it matches whole words.
-
Dark mode, measured across the whole site: 609 failures, of which 272 were one button
First whole-site dark-mode contrast sample: a research button at 2.31:1 on every project page, and a measuring error that hid 26 real failures.
-
A Gaussian process in a browser tab, and a band that was honest inside the data but not past it
A free Gaussian process tool fits seven kernels by marginal likelihood, checked against scikit-learn to 1e-9. On held-out CO2 months, its 95% band held 42%.
-
Open at 17:00, close at 09:00: red-teaming the shifts-from-sales planner
Ten faults seeded into the POS-sales shift planner, three caught. Reversed opening hours gave a silent empty plan; Swiss amounts were skipped.
-
Reading a 1 GB site twice instead of three times
One test hashed every file of the built site three times to compare three cache names. Reusing the digests cuts it from 7.1 s to 4.9 s.
-
A blank is not a zero wage: 34 seeded faults and two parsers that trusted Number()
34 faults seeded into four site and CI files; five got through. A manual hunt found the shared shop-rates bar read a stored blank as a $0 wage.
-
"Each empty stall costs you -$270": red-teaming six calculators that only knew how to win
Sixteen faults seeded, eight caught. Reading the code found a sentence that turned a loss into a gain, copied into six calculators.
-
The biggest discount, rounded up: a set-pricing answer that lost money
Eight faults seeded into a bundle pricing calculator, five escaped. Its biggest affordable discount often lost money, and could read 550%.
-
Red team: the merge-ref pwn request our checker missed, and dividend reinvestments the wash-sale page dropped
Mutation testing two tools found two real misses. The Actions checker ignored refs/pull/N/merge checkouts, and the wash-sale page refused reinvestment rows.
-
The lint saw 203 unguarded CSV exporters; there were 512. Red-teaming the tournament rating calculator
Ten faults seeded into new Elo and Glicko-2 code, seven caught. Player names could run as spreadsheet formulas, and the CSV lint only knew one name.
-
72 test suites no pull request ran, and the two that were red
72 of 121 test suites in our CI tooling ran on no pull request. Two were red on main. One script now runs every unwired suite in about 20 seconds.
-
The 2024 estimated-tax penalty divides by 366, and our worksheet divided by 365
A red-team run found two gaps from the IRS Form 2210 worksheet: 2024 rate periods divide by 366, and each late payment is rounded on its own.
-
The certificate that hid the takeover: why our subdomain checker could almost never say 'confirmed'
Our subdomain takeover checker probed HTTPS only, so dangling S3, Heroku and GitHub Pages CNAMEs failed TLS and could never read as confirmed.
-
The first week of December, read as seven months: red-teaming the schedule importer
Eight faults seeded into the schedule-export importer, two caught, and a real bug: a day-first week in early December came out as seven weeks.
-
The green test suite that ran half its tests
Splitting a slow test file showed that node --test with --test-force-exit was ending files early with exit 0. 641 tests became 587 and nothing failed.
-
The settlement date that made a wash sale out of nothing
A red-team pass on our wash-sale checker found three ways a broker export's column order gave a silently wrong answer. All three are fixed and tested.
-
The test that spent ten seconds waiting for a constant
A 31-test file took 21 seconds on 6 seconds of CPU. One test patched one timeout and waited out the other: 10 s idle. Patching it took the file to 10 s.
-
$1.250: what 58 US-dollar calculators showed a reader in Germany
A sweep loaded 1,227 calculators in US English and German. None computed a wrong number, but 58 printed dollar amounts in German format, like $1.250 for $1,250.
-
Two slashes past the systemd checker: red-teaming a unit-file linter
24 faults seeded into a systemd unit checker, 17 caught. Two real misses: a doubled slash hid a /tmp binary and a whole-filesystem ReadWritePaths.
-
A United Airlines refund is not rent: red-teaming three tax calculators
24 faults seeded in three tools, 18 caught. A rent pattern with no word boundaries booked airline refunds and bank interest as rental income.
-
Our wash-sale checker put a carried-over loss on the wrong shares, and an invariant found a second bug
Two basis bugs in the free wash-sale checker that overstated a later loss, how they were found, and the conservation test that now guards the class.
-
0x10 is not sixteen pesos: a red-team pass on the CFDI checker
JavaScript's Number() reads 0x10 as 16 and a blank as 0. The CFDI checker summed those values, then blamed correct totals. Two fixes and four new tests.
-
A backslash JavaScript throws away: eleven calendar exports that never escaped a semicolon
In JavaScript the string "\;" is a plain semicolon, so eleven of our .ics and vCard exporters never escaped one. The fix and the guard.
-
A blank price is not a free plan: one escaped fault and one real bug in the subscription price calculator
Eight faults seeded into the SaaS price calculator, seven caught. A manual hunt found a cleared price field showed a green 100% churn headline.
-
A calendar checker that read Tokyo time as UTC
The .ics checker flagged a valid Tokyo series as ending before it began. It compared clock digits instead of instants. Fixed, plus four RRULE rules it missed.
-
A calendar checker that rejected INTERVAL=02, and three faults its tests missed
Our .ics checker flagged INTERVAL=02 and COUNT=05 as errors although RFC 5545 allows them. Seeded faults found three more gaps in its tests.
-
A dollar sign before the minus turned a futures loss into a gain
Our 60/40 futures tax calculator read $-1,200 as +1,200 and 1.5E+04 as 1.5. A red-team run fixed the parser and the same bug in the wash-sale checker.
-
Our e-invoice checker told a Japanese seller to use a German VAT number
The page and CLI flagged PINT Japan, Singapore and A-NZ invoices with EU-only rules. The fix reads BT-24 and steps them aside on every route.
-
A negative loan paid the insurance: sixteen seeded faults in two creator and host analyzers
Sixteen faults seeded into the Turo earnings and YouTube RPM analyzers, four caught. A hand search found a negative loan quietly cancelling the insurance.
-
A typo in one amount should blame that amount, not the right ones beside it
Our Mexican CFDI checker read a non-number as 0, then flagged correct totals. A red-team run fixed it and added a test over 134 broken-number cases.
-
A warning that only fired for one spelling
24 seeded bugs in the new semver explainer: matching held against npm, but the English layer was untested and one warning missed four spellings of a range.
-
An unsigned NF-e is not always just unsigned
A red-team run seeded 10 faults in the NF-e checker; 7 were caught. The 3 escapes led to one real bug: a missing signature hid a broken file.
-
Boolean("no") is true: 64 bid calculators priced work you turned off
64 bid calculators read a checkbox sent as the word 'no' or 'off' as yes and priced the work anyway. One helper fix, a lint, and why the page never showed it.