-
A blank "can:" benched a child all game: red-teaming a youth lineup planner
12 faults seeded in the Youth Lineup Rotator, 9 caught, all 3 holes closed; the code read found a roster line that silently kept a child off the field.
-
Our schedule comparison could compare your project with a different one
A red-team run on our new P6 XER update comparison found three real defects and seven test gaps in a day-old feature. All are fixed and tested.
-
A share link could run script on eight bid calculators. A new sweep found them
A browser sweep typed an inert HTML probe into 1,012 tool pages. 13 rendered it as markup, 8 of them through a share link. All 13 now escape.
-
Blank, zero and minus one in every field: what 18,000 button clicks found in our tools
We typed blank, 0 and -1 into every field of 1,382 pages and clicked every button. Eleven tools showed $Infinity, NaN or a silent click.
-
A hundred dollars plus ten thousand yen came out as two hundred dollars
A red-team run found MRR Pulse's browser demo adding yen to cents. It now keeps the most common currency and lists the other rows as skipped.
-
One error message, eleven tools: "must be between 0 and Infinity"
A browser sweep found three tools saying a value must be between 0 and Infinity. A grep found eight more with the same code, and a lint now blocks it.
-
Our browser sweeps never ran the code they were testing, and two tools were broken for five days
Chromium won't load module scripts from file://, so five of our page sweeps tested code that never ran. Over http they found ten bugs.
-
A plural offset can hide a missing "one" from your checker
With offset:1, ICU picks the plural category from n minus 1 but matches =1 against n, so =1 no longer covers "one". Our checker now flags it.
-
A comment hid the lock_timeout, and '0h' passed for a real one
24 faults seeded in a PostgreSQL migration lock checker, 18 caught; two real bugs in how it reads SET lock_timeout, one a false alarm and one a false all-clear.
-
A dollar sign dropped the student: red-teaming a tutoring scheduler and a robots.txt checker
20 faults seeded in two tools, 10 caught at first; five guard tests added, and a fix for a price typed as $25 making the scheduler skip the student.
-
Two ways to set lock_timeout that the lock checker did not see
20 faults seeded in the PostgreSQL migration lock checker, 16 caught; DISCARD ALL and set_config() changed lock_timeout unseen. All fixed.
-
Two rows, one subscription: red-teaming an MRR dashboard
20 faults seeded in MRR Pulse, 18 caught, both holes closed; the code read found a CSV whose headline MRR and plan breakdown disagreed.
-
The alert that said it would fire in six hours, and never could
24 faults seeded in an SLO alert planner and an HVAC load calculation, all 8 escapes closed; one alert read both unreachable and six hours from firing.
-
16 of our servers let a caller choose its own rate-limit bucket
Our support agent keyed its rate limits on the client-written end of X-Forwarded-For, and so did 15 more servers. All fixed, with a CI guard.
-
A blank cell is not a free customer: two quiet CSV bugs in an MRR dashboard
MRR Pulse read a blank Stripe Amount as a $0 subscription and called a 0-seat row an unknown interval. Both fixed; sample data now pinned.
-
A card number with its security code after it slipped past our support agent's card check
A card number typed with its CVV ran into one long digit run, failed Luhn and was answered, not handed off. Fixed, with cut numbered steps.
-
A date that does not exist moves your revenue: strict CSV import in Rev Rec and MRR Pulse
JavaScript reads 2026-02-30 as 2 March and '€ 1.000' as one euro. Two of our Stripe finance tools now skip those rows with a reason instead of guessing.
-
A dollar sign outside the brackets turned refunds into income in 48 tools
Our CSV parsers read ($100.00) as a negative and $(100.00) as a positive. Excel writes the second one. The fix, and the test that stops the pattern coming back.
-
A lock_timeout that never switched off
A red-team run seeded 24 faults into three products, closed every gap, and found the migration lock checker treating lock_timeout as permanent once set.
-
A team called constructor: two bugs found in a day-old league page
Team and duty names like constructor or toString read inherited JavaScript keys: one crashed the new league page, the other switched off a fairness rule.
-
Fuzzing fifty repair buttons: a repair should not want a second pass
We mutated the sample files of 50 free file checkers and repaired each mutant twice. 15 fixes later, a seeded test guards every one.
-
A trial that never paid is not churn: the MRR history that counted trials as revenue
MRR Pulse rebuilt a year of MRR starting every subscription at created, so trials showed as revenue and trials that never paid showed as churn.
-
A day stamp with a trailing T: what three red-team campaigns found
24 faults seeded in a bid calculator, a usage counter and the deploy build: 14 caught, test gaps closed, and a day-stamp check for 1,286 counters.
-
Red team: a kid named =HYPERLINK, and 152 more spreadsheets that would have run it
A red-team run seeded 22 faults in two tools, found a CSV formula-injection hole in a lineup planner and closed it in 152 exporters.
-
A price doubling read as a revenue loss, once the numbers got big enough
A red-team run caught 16 of 24 seeded faults, closed all eight gaps, and found a SaaS price calculator calling a price doubling a loss on overflow.
-
A table rewrite hidden by two pairs of quotes
A red-team run on the PostgreSQL migration lock checker caught 29 of 38 seeded faults and found a quoted schema name hiding a full table rewrite.
-
One typo in an end date booked a whole year's revenue in January
A red-team run seeded 16 faults into two tools, closed both test gaps, and found a revenue schedule booking a full year in month one after an end-date typo.
-
"On day last of the year": two wording bugs in the RRULE explainer
20 faults seeded into the RRULE explainer: 14 caught, three test gaps closed, and two wording bugs fixed, like "on day last of the year".
-
One backslash hid a table lock: red-teaming a migration lock checker
20 faults seeded in a PostgreSQL migration lock checker, 17 caught; reading the scanner as an attacker found two inputs that hid every statement after them.
-
The subscription that never paid: red-teaming an MRR dashboard
18 faults seeded in an MRR dashboard and a lock checker, 13 caught, all 18 after new tests; the code read found never-paid Stripe subscriptions counted as MRR.
-
The yen sign nobody stripped: red-teaming a revenue schedule
32 faults seeded in Rev Rec, 27 caught, every real hole closed; the code read found yen, rupee and 'USD 100' amounts skipped as not a number.
-
Asking Rev Rec for a journal through March gave you every month
Months stored as YYYY-MM text sort correctly only when every month has two digits. An unchecked ?through=2026-3 exported the whole year, and nothing flagged it.
-
Rev Rec was booking VAT as revenue on new Stripe accounts
A red-team pass on the self-hosted revenue schedule found two real bugs: Stripe's newer tax field went unread, and invoices paid after net terms never arrived.
-
ROLLBACK TO SAVEPOINT is not a rollback: a migration checker read it as one
Our PostgreSQL migration checker read ROLLBACK TO SAVEPOINT as the end of a transaction, so a failing CREATE INDEX CONCURRENTLY read clean. Fixed.
-
Seven bugs MRR Pulse's tests would have let through
We seeded 18 small faults into MRR Pulse's metrics and alert code. Its 29 tests caught 11. Five new tests now catch all 18.
-
Seven tools that read 19,99 as 1999
Seven tools accepted European semicolon CSVs, then read the decimal comma as a thousands separator, 10 to 100 times off. All fixed; a lint blocks the next.
-
The fix that reached three of thirty-nine copies
A guard for a throwing localStorage read reached 3 of 39 copies of one function; the other 36 calculators hid their answer. A token-diff report found it.
-
The tests that left two gigabytes behind
One run of the site builder's tests left 2 GB of dead build output in the temp directory. Four cleanups and one shared read later, it leaves 4 MB.
-
A bank charge bigger than the last invoice
A short-pay bigger than the last named invoice gave it a negative application. Found by a red-team run, fixed and guarded.
-
A capacity of three hundred million: red-teaming a stable matching tool
Ten seeded faults and an attacker's read of the new stable matching tool found two real bugs: a typed capacity that froze the page and same-named sides.
-
A capital G would have kept the site out of Search Console
Today's red-team run seeded 20 faults; the tests caught 16 and two more were harmless. The real find was a config file that ignored a misspelt key.
-
A commented-out door the IFC checker still checked
Our IFC reader found entities by pattern, so a commented-out record came back as a real door. A red-team run found it, fixed it and added guard tests.
-
When a crash looks like "over budget": exit codes in 15 pricing calculators
15 pricing CLIs promise exit 1 for over budget and 2 for bad input. Bad input crashed them with exit 1. Now it exits 2, and a CI check keeps it so.
-
A European CSV, and a missing reading that became a zero
Red-teaming the method comparison tool: a semicolon CSV with decimal commas was silently misread, and a null reading entered every fit as 0.
-
Six of eight seeded faults on the Stories page got past its tests
A red-team run seeded 8 faults into the Stories page. Its tests caught 2. Five were CSS a browser drops without an error; a new selector lint now catches them.
-
Does pressing Enter wipe the calculator? 139 pages, no
Pressing Enter in a form with no submit handler reloads the page and clears it. A new Chromium sweep pressed Enter on 139 pages. None lost input.
-
Red-teaming a tip-credit calculator and a DKIM key parser: 22 faults, 13 caught
22 faults seeded into a FICA tip credit calculator and a DKIM key parser: 13 caught, seven holes closed with seven small tests, two proven harmless.
-
A red-team pass on the new exact-test calculator: thirteen seconds down to thirty milliseconds
Seeding faults into a new exact test calculator found a 13-second page freeze, a silently ignored one-sided option and a NaN% summary. All fixed, with tests.
-
A blank price was read as $0 in 109 bid calculators
A red-team run on the landscape lighting bid calculator found that a price of spaces counted as $0. The same check had been copied into 108 other calculators.
-
A line break inside a quoted CSV cell, and three tools that split it
A red-team run found a feed checker splitting one multi-line description into two broken items. Three tools fixed; CI now scans 156 CSV parsers.