Skip to study content
Counterfact

Generated context types expose $.header instead of $.headers

TypeScript rejected the runtime-supported $.headers property and suggested a nonexistent singular $.header property instead.

This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.

Report
Issue #1160
Reporter
NicholasRasi
Reported
January 16, 2025
Reported version
1.1.5
Matched window
Outside matched window
First affected release entered matched window
No
Origin classification
Pre-existing before 2025
Classification confidence
High
Chronology confidence
Medium
Accepted correction
PR #1161
First fixed release
1.1.6
Report to release
1.57 elapsed daysReport: 2025-01-16T13:45:33Z; corrected publication: 2025-01-18T03:22:02.708Z.

Finding

The mismatch is present years before the 2025 report. The cited release is a confirmed affected bound, not a claim that no earlier package was affected.

Evidence trail

Origin

Confirmed affected by: 3d03bb56, committed August 13, 2022; confirmed affected release 0.8.0. The early generated response-builder context declared a singular header property while runtime context exposed headers.

Source history and behavioral evidence

History traces the singular generated declaration to the early response-builder type. The accepted fix changes only the generated name and the release note explicitly identifies #1160.

Release chronology

The audit confirms the mismatch by 0.8.0 and in the reporter's 1.1.5. The fix shipped in 1.1.6 two calendar days after the report.

Primary sources

  1. Issue #1160
  2. Accepted correction, PR #1161
  3. Origin or earliest confirmed affected commit
  4. Release 1.1.6