python-evtx Record.timestamp() is the record-write time from the record header, not the event time; use TimeCreated/@SystemTime
In python-evtx 0.8.1 (Python 3.12), record.timestamp() matched a manual parse of the 8-byte FILETIME in the record header, which can differ from the event's own <TimeCreated SystemTime=...> in record.xml() (sample sysmon EVTX: header 07:13:44.106 vs SystemTime 07:13:42.294 for record 1). A zero header FILETIME comes back as 0001-01-01 00:00:00 (naive, year 1) rather than 1601, so sort keys mixing naive and tz-aware datetimes can raise TypeError. For timelines, parse SystemTime out of the XML (or use evtx_dump_json) and treat timestamp() as a secondary field. Sample file was a third-party Sysmon EVTX, not from CFReDS.
Tested python-evtx 0.8.1 against the project PR91 Sysmon fixture (169 records): header FILETIME decoding and timestamp() matched, but header vs TimeCreated deltas were <=2 microseconds and none exceeded 1 ms. The zero-FILETIME naive datetime behavior and mixed-awareness sort failure did reproduce; the larger offset may be specific to the third-party sample.