Skip to study content
Counterfact

Case records

These detailed external-report cases from 2025–2026 trace reported behavior through the available source and release evidence. Matched-window membership remains separate from defect origin. The public-record census provides the broader candidate record.

2025 product cases

ReportReportedMatched windowOrigin classificationFirst fixed release
#1160: The generated context used the wrong headers propertyNicholasRasi · GeneratorJanuary 16, 2025Outside matched windowPre-existing before 20251.1.62 calendar days after report
#1244: External YAML references broke Swagger UIsugiruu · RuntimeMarch 28, 2025IncludedPre-existing before 20252.2.1357 calendar days after report
#1370: Content-type parameters hid the JSON shortcutIhorR-DevBrother · GeneratorAugust 14, 2025IncludedPre-existing before 20251.4.26 calendar days after report
#1381: Colon routes failed on Windowsxehmer · GeneratorSeptember 2, 2025IncludedPre-existing before 20251.4.53 calendar days after report

2026 product cases

ReportReportedMatched windowOrigin classificationFirst fixed release
#1506: Nested schemas made optional properties requirednkincy · GeneratorFebruary 25, 2026Outside matched windowPre-existing before 20262.0.01 calendar day after report
#1515: Root middleware did not runvglaeser · RuntimeMarch 2, 2026Outside matched windowPre-existing before 20262.2.017 calendar days after report
#1516: Invalid operation IDs broke generated TypeScriptnkincy · GeneratorMarch 2, 2026Outside matched windowDefect in a 2026 feature2.0.10 calendar days after report
#1617: Reserved operation IDs broke generated TypeScriptdissemond-bitside · GeneratorApril 2, 2026IncludedDefect in a 2026 feature2.5.01 calendar day after report
#1618: Schema-less responses broke type generationdissemond-bitside · GeneratorApril 2, 2026IncludedPre-existing before 20262.5.01 calendar day after report
#1619: Colon routes produced the wrong import pathdissemond-bitside · GeneratorApril 2, 2026IncludedPre-existing before 20262.5.01 calendar day after report
#1842: Path Item metadata crashed the generatordissemond-bitside · GeneratorApril 13, 2026IncludedPre-existing before 20262.8.11 calendar day after report
#1933: Exploded object query parameters were not assembleddissemond-bitside · RuntimeApril 21, 2026IncludedPre-existing before 20262.10.04 calendar days after report
#1971: Path-level parameters were ignoreddissemond-bitside · GeneratorApril 30, 2026IncludedPre-existing before 20262.11.05 calendar days after report
#2075: The package ran an obsolete postinstall hookiki · PackagingMay 15, 2026IncludedPre-existing before 20262.12.01 calendar day after report

Process-quality incident: issue #2348

Release 2.16.2 lacked normal public provenance signals. The release was authentic, but the missing tag, GitHub release, and green publishing provenance made a reasonable user question whether it was legitimate. GitHub-based publishing resumed with release 2.16.5. The incident is included in the study’s interpretation but excluded from product-defect percentages because the published code was authentic.