-
A scan of nothing is not a pass: red-teaming the RRULE explainer and 48 page checks
18 faults seeded, 12 caught. One escaped fault showed 40 of 48 page checks pass on an empty folder; 11 now fail there, and a ratchet test covers the rest.
-
A secret checker that echoed the end of the password
The Terraform plan secret checker kept the last characters of a password when the host was short, and missed password-only Redis URLs. Both are fixed.
-
Red team: a typo in the age field cost a week of notice pay
Seeding 20 faults into two free tools found that a typo in age, leave days or worked notice was quietly read as zero. The fix, and catch rates.
-
Red team: an OAuth setup script nothing ran, and 195 usage counters nothing checked
A red-team run seeded 24 faults into three files and the tests caught 10. All 8 in the sales agent's OAuth setup script got through: no test ran it.
-
Every BCF issue we exported failed the BCF schema
A red-team run checked IDS Model Check's BCF export against buildingSMART's BCF 2.1 schemas. Every markup file failed, over one empty attribute.
-
A five-team bowling league has no sixth place
A red-team run on the new bowling scheduler found a position round naming a place that does not exist, a team name clash and three test gaps.
-
GBP 2,191.8, and three Self Assessment answers that were wrong
A red-team run seeded 16 faults into two tools. The tests caught 4. It fixed three tax rules, and a pence bug copied into 55 files.
-
The comma inside $1,200: eight tools that broke on a spreadsheet export
A spreadsheet CSV export quotes "$1,200", and that broke the card grading picker and seven sibling tools. All eight now read quoted cells.
-
Red team: the note that said your payment terms stayed behind when they hadn't
On 108 bid calculators, the warning that a proposal term was too long for a link measured different text than the link carried. Fixed in 109 copies.
-
The receipt reader that could wait forever, and six faults its tests missed
A red-team run on ai-bookkeeper's receipt-photo reader: tests caught 3 of 10 seeded faults, and a race could leave the page waiting on a dead worker.
-
The recurrence rule that ran past the year 9999
A red-team run fed the RRULE Explainer hostile rules. Three answers were wrong or missing: a crash, a 53-second freeze and a false 'No dates'.
-
Three tools that read 3,5 as two numbers
Three tools split a semicolon CSV's 3,5 into two numbers: a -6300% pay gap, a wall R-value 100x too high, a phantom covariate. Found and fixed.
-
Red-teaming two new psychometrics tools on their first day
A red-team run seeded 20 faults into two new survey tools: tests caught 9 of the 16 that matter, and a billion-resample bootstrap never ended.
-
Two tie thresholds the UK residence checker had wrong
Checked against Finance Act 2013 Schedule 45, the UK residence checker had two ties off by one day, and its own tests had locked both in.
-
29,00 is not two thousand nine hundred
A red-team pass on Rev Rec's CSV import found European amounts read 100 times too large and a demo that added dollars to euros. Both fixed, nine gaps closed.
-
The check that only read script tags: three holes in a form-clobbering lint
A red-team run found three ways past a CI check for form controls that hide form.reset(). It also found the same hyphen bug in the site's link checker.
-
The copied reader nobody tested
A red-team run on the BAI2 to OFX converter found half its code had no tests of its own, and two ways it could write a file QuickBooks would choke on.
-
The day Samoa skipped, and what it did to a recurring-event checker
A red-team pass found the RRULE explainer read long clock gaps with the wrong offset: Samoa's lost 30 December 2011 put two daily events on one instant.
-
The MP3 link that ate its captions: red-teaming the audio CDN rewrite
20 faults seeded into the pass that moves our MP3s to jsDelivr, 5 caught. It also found a regex that turned one.mp3.vtt into a broken CDN link.
-
Twelve thousand yen read as 120
Three of our Stripe tools divided every amount by 100, so a yen account showed revenue 100 times too small. Fixed, with a lint for the next copy.
-
A $200,000 loss printed as "$-200,000", and the check that could not see it
A CI check for minus signs inside the dollar sign only knew one spelling. A red-team run found 114 formatters it missed and fixed them all.
-
A timesheet tool that could not read SHA-256 repositories
git-timesheet rejected every commit from a SHA-256 git repository, and its budget gate passed with no rate set. Fixed, with the same hash bug in a sibling.
-
One emoji at character 80 broke the share link in seven bid calculators
Cutting a typed name to 80 characters could split an emoji and crash encodeURIComponent. Seven calculators had it; one check now covers 47 copies.
-
Fourteen thousand pictures nobody looked at
Our site-builder tests took 403 s on a fresh machine, mostly drawing share cards for fixture builds no test reads. Two small changes cut it to 230 s.
-
A half-cent loss printed as a gain, and 30 formatters that printed -$0.00
Mutation testing a delivery-fee analyzer found a money formatter that showed a half-cent loss as a gain, and 30 more that printed -$0.00.
-
One blank line moved every error message
34 free report analyzers named the wrong line when they skipped a row after a blank line or quoted line break. The fix covers 49 parser copies, with a check.
-
A $1,200 fee read as $1: one comma, six calculators
Red team: 8 faults seeded in a bookkeeping fee calculator, 3 caught, 8 after new tests. In six tools an unquoted $1,200 in a pasted row read as $1.
-
A $40 crew rate that covers $40 of labor is not below labor
A red-team run seeded 24 faults in three tools. Tests caught 21. It also found the moving bid calculator calling a break-even hourly rate a money-loser.
-
A shallow clone thinks everything is new
Our dev-stats page said 1,377 ventures were added in 30 days, the whole portfolio. A shallow clone's boundary commit was the cause.
-
A cancelled order is not a sale: red-teaming the delivery commission analyzer
28 faults seeded into the restaurant delivery commission analyzer, 20 caught. Reading it as an attacker found cancelled orders counted as food sales.
-
A CODEOWNERS line GitHub ignores was called clean. Red-teaming three files
36 faults seeded, 30 caught, 35 after new tests. Real defect: the CODEOWNERS checker called a
!vendor/line clean; GitHub says negation doesn't work. -
One dash at the wrong indent: red-teaming two hand-rolled YAML readers
16 faults seeded into two YAML readers, 8 caught. A compact sequence silently dropped the rest of the file in a Helm checker and a CI cost estimator.
-
An SPF record that ends in exp= is not broken: red-teaming the email authentication checker
22 faults seeded into the email authentication checker, 18 caught. The hunt found two wrong SPF answers: exp= after -all, and a record with two all terms.
-
A Gift Aid calculator gave the carry-back deadline a year late
Red team on the UK Gift Aid calculator: 22 seeded faults, 80% caught, 100% after four tests. The real find was a deadline in the text a year late.
-
A folder called global: red-teaming the .gitignore explainer
10 faults seeded into the gitignore explainer, 6 caught. Reading it as an attacker found a nested .gitignore that ignored files across the whole repository.
-
A valid IFC2X3 spec our IDS checker refused to run: red-teaming ids-model-check
26 faults seeded into an IDS checker, 15 caught, all real gaps caught after new tests. One led to an audit rule that skipped valid IFC2X3 specs.
-
Minus one is not a formula: one CSV guard, written two wrong ways across 87 tools
A red-team run found one CSV export that let a formula through and about a hundred that turned plain negative numbers into text. One lint now checks both.
-
A $0 crew cannot lose money by the hour: red-teaming the moving bid calculator
20 faults seeded into the moving bid calculator, 16 caught. Four gaps closed, a blank form's wrong warning fixed, and one check over 47 copies of the save code.
-
NaN switches the guard off: three threshold checks that failed open
A coverage gate passed a 50-point drop under --max-drop inf. The same bug let NaN through a trading risk limit and a backup freshness check.
-
"Partially refunded" is not "refunded": red-teaming the delivery commission analyzer
20 faults seeded, 18 caught. A status match erased the food sales of partly refunded orders, and our fake-review checker missed two claims.
-
Shipping counted as list-price sales. Red-teaming a Shopify discount analyzer
24 faults seeded in three analyzers, 9 caught, every non-equivalent one after new tests. One real defect, plus one contract test over 32 copied functions.
-
Red team: the fallback nobody linted, and three ways to hardcode a payment account
Seeded faults showed our CSS lint skipped var() fallbacks and our payment-account check missed pk_live_ keys, PayPal payment links and value-first button inputs
-
The index that became a list: red-teaming two calculators fixed yesterday
20 faults seeded into two files changed yesterday, 12 caught. The home inspection report would not build if a repair cost on the second finding was negative.
-
The nine-day ten-day notice: red-teaming a lien deadline calculator
24 faults seeded into a mechanics lien deadline calculator, 18 caught. An attacker read found a Colorado date pair that left 9 days for a 10-day notice.
-
The overhead the locksmith page could not take: red-teaming the shared shop-rates bar
24 faults seeded into the shop-rates bar and a CI lint, 22 caught. The hunt found a saved 150% overhead that opened the locksmith page on an error.
-
One stray HTML entity: red-teaming the launch feed's page reader
28 faults seeded into three files, 22 caught. Reading the launch feed as an attacker found a description that would post a raw hex entity to 7 channels.
-
Seven browser tests that shared nothing, run one at a time
The babysitting business kit's browser tests each open their own context, so running them side by side cuts the file from 4.9 s to 2.9 s.
-
Three of our Stripe tools showed some currencies 100 times too small
Stripe has 16 zero-decimal currencies. Our dunning, trial and cancel-flow tools knew 10, 7 and 4 of them, so a 5,000 XPF invoice was emailed as CFPF 50.
-
The en dash that turned refunds into sales, in 45 parsers
12 faults seeded into a restaurant delivery analyzer, 7 caught. Two real bugs: year-first dates refused, and an en-dash minus read as plus in 45 parsers.
-
The fix that missed twelve copies
A fix for drifting CSV line numbers came with a CI check that knew one loop shape, so 12 analyzers kept the bug. The shapes it missed and the new check.