diaggrok 2026.11.8__tar.gz

diaggrok-2026.11.8/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

diaggrok-2026.11.8/PKG-INFO

@@ -0,0 +1,160 @@
+Metadata-Version: 2.4
+Name: diaggrok
+Version: 2026.11.8
+Summary: Qualcomm DIAG log code parser library
+Author: Luke Jenkins
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/lukejenkins/diaggrok
+Project-URL: Source, https://github.com/lukejenkins/diaggrok
+Project-URL: Changelog, https://github.com/lukejenkins/diaggrok/releases
+Keywords: diag,modem,cellular,baseband,lte,5g
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: Telecommunications Industry
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Communications
+Classifier: Topic :: System :: Hardware
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# diaggrok
+
+> Part of the **[cellular `diag*` toolkit](https://github.com/lukejenkins/cellular#the-diag-toolkit)**: start there for how the capture/decode pieces fit together.
+
+A 100% reverse engineered library for parsing the diagnostic (DIAG) logs of mobile devices — specifically the `LOG_F` records that modern cell modems built on Qualcomm chipsets emit when you put them into diagnostic mode.
+
+If you've ever pointed a vendor log viewer, QCSuper, or SCAT at a modem and wondered what all those `0x1526`-style log codes actually *mean*, that's the itch this scratches. diaggrok takes the raw bytes of a DIAG log record and hands you back named, typed fields.
+
+## What's in here
+
+This repo is a curated public **carve** out of a much larger private working tree — it ships the parsers I've cleaned up enough to stand behind on their own. As of `v2026.10.04` that's:
+
+* **188 log-code parsers**
+* Pure Python, **zero dependencies**, Python 3.11+
+* Apache-2.0 licensed
+
+Coverage, by area:
+
+* **GNSS**: fixes, per-SV measurements across GPS / GLONASS / Galileo / BeiDou / QZSS / SBAS / NavIC (including the L5 / E5a / B1C reports), clock and time state, ephemeris, SBAS demod, RF front-end and power-profiling reports, NMEA-over-DIAG
+* **LTE**: ML1 / LL1 cell search and measurements (serving, neighbour, IRAT-to-NR), MAC RACH and transport blocks, PDCP, RRC OTA plus MIB / SIB / serving-cell info / CA combos, NAS EMM and ESM messages and state
+* **5G NR**: L1 / ML1 measurements and per-beam blocks, cell search, CDRX, MAC, RRC OTA plus MIB / serving-cell / configuration / CA combos, NAS 5GMM and 5GSM messages and state
+* **2G / 3G**: a handful of GSM L1 acquisition and measurement records, GSM RR signalling, WCDMA PN search results, and UMTS NAS PLMN lists
+* **Everything else**: IMS SIP and registration, SIM / UICC APDU traces, QMI and QCRIL logging, the IPA data path, and some thermal, battery and coexistence reports
+
+Every parser was reverse engineered against real captures. Most of the early work was on a Quectel **RM520N-GL** (SDX62); this release adds parsers validated on chipsets from the MDM9x07 generation through SDX72. Where a decoded field could be matched against the modem's own debug messages (F3 traces), it was, and each parser's metadata says where its decode came from (see `parser_info()` below).
+
+The thing I care most about: each parser knows its own byte layout and **refuses to guess**. If a record isn't the size it was reverse engineered against, or carries a version byte the parser doesn't know, the parser returns `None` instead of emitting plausible-looking garbage. Size invariance is not format invariance, and I'd rather see a parse-rate drop on a new firmware than trust a silently mis-decoded field. Those drops aren't silent either: when a registered parser declines a record, diaggrok logs a rate-limited warning, so a gap in coverage shows up in your logs instead of hiding in them.
+
+(`EXTRACT_MANIFEST.json` in the repo root lists exactly which log codes and modules made it into this carve.)
+
+## Installation
+
+Not on PyPI yet — install straight from GitHub:
+
+```bash
+pip install "diaggrok @ git+https://github.com/lukejenkins/diaggrok@main"
+```
+
+## Usage
+
+The high-level entry point is `parse()`: give it a log code, a timestamp, and the raw payload bytes, and get back a decoded object (or `None` if nothing's registered for that code).
+
+```python
+import diaggrok
+
+result = diaggrok.parse(0x1526, log_time, payload)
+if result is not None:
+    print(result.to_dict())
+```
+
+If you're starting from a raw DIAG `LOG_F` (opcode `0x10`) frame, peel off the outer/inner headers first — `parse_outer_frame()` hands back the log code as `log_type`:
+
+```python
+from diaggrok import parse_outer_frame, parse
+
+pending, log_type, log_time, log_payload = parse_outer_frame(frame_bytes)
+result = parse(log_type, log_time, log_payload)
+```
+
+### Reading capture files
+
+If you've got a whole capture on disk, `diaggrok.dlf.iter_records()` works out the framing for you (flat DLF, raw HDLC, or QMDL2) and yields `(log_code, timestamp, payload)` for every log record:
+
+```python
+from pathlib import Path
+
+import diaggrok
+from diaggrok.dlf import iter_records
+
+for code, ts, payload in iter_records(Path("capture.dlf").read_bytes()):
+    result = diaggrok.parse(code, ts, payload)
+    if result is not None:
+        print(hex(code), result.to_dict())
+```
+
+`apps/diagreplay/` wraps that in a small reader that also handles `.zst` / `.gz` compressed captures and can filter by log code. Its command line lists the records in a capture (timestamp, code, length, and with `--json` the raw payload as hex) without decoding them, which is handy for a first look:
+
+```sh
+cd apps/diagreplay
+python -m diagreplay capture.dlf.zst --code 0x1526 --json
+```
+
+### What's supported
+
+Want to see what's supported, or poke at a parser's metadata (where the decode came from, which payload versions it accepts, how many fields it identifies)?
+
+```python
+diaggrok.registered_codes()    # -> [0x10BA, 0x117E, ...]
+diaggrok.parser_info(0x1526)   # -> ParserEntry(name='0x1526', source_type='re', ...)
+```
+
+### Bring your own parsers
+
+You don't have to fork to extend it. Drop a `.py` file that calls `@register(...)` into `~/.diaggrok/plugins/` (or point `DIAGGROK_PLUGIN_DIR` at a directory of them), then:
+
+```python
+diaggrok.load_plugins()
+```
+
+## A note on privacy
+
+Some of these log codes carry personal data, because the modem logs it: NAS and RRC messages can include subscriber and device identifiers, the IMS parsers decode SIP traffic and registration identities, the SIM parsers decode APDUs, and GNSS fixes are your location. diaggrok decodes what's in the record and does not redact anything. If you share decoded output (or the captures themselves), check what's in them first.
+
+## Changes between releases
+
+Releases are tagged `vYYYY.MM.DD`. A parser's record shape is part of the public interface, so [CHANGELOG.md](./CHANGELOG.md) lists every renamed, removed, or re-typed field. `v2026.10.04` has breaking changes to 22 existing parsers (mostly placeholder fields replaced by real decodes, plus `0x4179`, which turned out to be a WCDMA record rather than LTE). Read the changelog before upgrading from `v2026.08.23`.
+
+## Scope, and some honesty
+
+This is carved out of an active reverse-engineering project, so a few things are true and worth saying out loud:
+
+* It only covers modems built on Qualcomm chipsets. Other basebands aren't in scope here.
+* A parser makes it into this repo only once it's been checked against real captures. Plenty of log codes I've looked at aren't here yet, and the ones that are don't all decode every field. Unknown bytes stay as raw values rather than getting a guessed name.
+* 2G/3G is thin — those technologies had been sunset before I got into cellular based tech, and the projects in Kudos below do that far better, so use them for it.
+
+## Kudos
+
+This software is strongly inspired by a few other projects. In many cases they still do a better job parsing logs into usable data. This is especially true for 2G and 3G technologies that had been sunset before I got into cellular based tech. They also have a much longer track record and support ecosystem, so check them out:
+
+* https://osmocom.org/projects/baseband/wiki/Ccch_scan
+* https://github.com/p1sec/qcsuper
+* https://github.com/fgsect/scat
+
+None of the code from these projects is in diaggrok.
+
+## AI Disclaimer
+
+The AI 'bots are VERY good at finding patterns and matching values, exactly what one needs for taking documented output (e.g. AT commands) and matching it up to help you decode a publicly undocumented protocol (e.g. diag logs from a cell modem). If you're opposed to using this kind of work, there are other open source options and some commercial options that you should seek out.
+
+## License
+
+Apache-2.0. See [LICENSE](./LICENSE).

diaggrok-2026.11.8/README.md

@@ -0,0 +1,132 @@
+# diaggrok
+
+> Part of the **[cellular `diag*` toolkit](https://github.com/lukejenkins/cellular#the-diag-toolkit)**: start there for how the capture/decode pieces fit together.
+
+A 100% reverse engineered library for parsing the diagnostic (DIAG) logs of mobile devices — specifically the `LOG_F` records that modern cell modems built on Qualcomm chipsets emit when you put them into diagnostic mode.
+
+If you've ever pointed a vendor log viewer, QCSuper, or SCAT at a modem and wondered what all those `0x1526`-style log codes actually *mean*, that's the itch this scratches. diaggrok takes the raw bytes of a DIAG log record and hands you back named, typed fields.
+
+## What's in here
+
+This repo is a curated public **carve** out of a much larger private working tree — it ships the parsers I've cleaned up enough to stand behind on their own. As of `v2026.10.04` that's:
+
+* **188 log-code parsers**
+* Pure Python, **zero dependencies**, Python 3.11+
+* Apache-2.0 licensed
+
+Coverage, by area:
+
+* **GNSS**: fixes, per-SV measurements across GPS / GLONASS / Galileo / BeiDou / QZSS / SBAS / NavIC (including the L5 / E5a / B1C reports), clock and time state, ephemeris, SBAS demod, RF front-end and power-profiling reports, NMEA-over-DIAG
+* **LTE**: ML1 / LL1 cell search and measurements (serving, neighbour, IRAT-to-NR), MAC RACH and transport blocks, PDCP, RRC OTA plus MIB / SIB / serving-cell info / CA combos, NAS EMM and ESM messages and state
+* **5G NR**: L1 / ML1 measurements and per-beam blocks, cell search, CDRX, MAC, RRC OTA plus MIB / serving-cell / configuration / CA combos, NAS 5GMM and 5GSM messages and state
+* **2G / 3G**: a handful of GSM L1 acquisition and measurement records, GSM RR signalling, WCDMA PN search results, and UMTS NAS PLMN lists
+* **Everything else**: IMS SIP and registration, SIM / UICC APDU traces, QMI and QCRIL logging, the IPA data path, and some thermal, battery and coexistence reports
+
+Every parser was reverse engineered against real captures. Most of the early work was on a Quectel **RM520N-GL** (SDX62); this release adds parsers validated on chipsets from the MDM9x07 generation through SDX72. Where a decoded field could be matched against the modem's own debug messages (F3 traces), it was, and each parser's metadata says where its decode came from (see `parser_info()` below).
+
+The thing I care most about: each parser knows its own byte layout and **refuses to guess**. If a record isn't the size it was reverse engineered against, or carries a version byte the parser doesn't know, the parser returns `None` instead of emitting plausible-looking garbage. Size invariance is not format invariance, and I'd rather see a parse-rate drop on a new firmware than trust a silently mis-decoded field. Those drops aren't silent either: when a registered parser declines a record, diaggrok logs a rate-limited warning, so a gap in coverage shows up in your logs instead of hiding in them.
+
+(`EXTRACT_MANIFEST.json` in the repo root lists exactly which log codes and modules made it into this carve.)
+
+## Installation
+
+Not on PyPI yet — install straight from GitHub:
+
+```bash
+pip install "diaggrok @ git+https://github.com/lukejenkins/diaggrok@main"
+```
+
+## Usage
+
+The high-level entry point is `parse()`: give it a log code, a timestamp, and the raw payload bytes, and get back a decoded object (or `None` if nothing's registered for that code).
+
+```python
+import diaggrok
+
+result = diaggrok.parse(0x1526, log_time, payload)
+if result is not None:
+    print(result.to_dict())
+```
+
+If you're starting from a raw DIAG `LOG_F` (opcode `0x10`) frame, peel off the outer/inner headers first — `parse_outer_frame()` hands back the log code as `log_type`:
+
+```python
+from diaggrok import parse_outer_frame, parse
+
+pending, log_type, log_time, log_payload = parse_outer_frame(frame_bytes)
+result = parse(log_type, log_time, log_payload)
+```
+
+### Reading capture files
+
+If you've got a whole capture on disk, `diaggrok.dlf.iter_records()` works out the framing for you (flat DLF, raw HDLC, or QMDL2) and yields `(log_code, timestamp, payload)` for every log record:
+
+```python
+from pathlib import Path
+
+import diaggrok
+from diaggrok.dlf import iter_records
+
+for code, ts, payload in iter_records(Path("capture.dlf").read_bytes()):
+    result = diaggrok.parse(code, ts, payload)
+    if result is not None:
+        print(hex(code), result.to_dict())
+```
+
+`apps/diagreplay/` wraps that in a small reader that also handles `.zst` / `.gz` compressed captures and can filter by log code. Its command line lists the records in a capture (timestamp, code, length, and with `--json` the raw payload as hex) without decoding them, which is handy for a first look:
+
+```sh
+cd apps/diagreplay
+python -m diagreplay capture.dlf.zst --code 0x1526 --json
+```
+
+### What's supported
+
+Want to see what's supported, or poke at a parser's metadata (where the decode came from, which payload versions it accepts, how many fields it identifies)?
+
+```python
+diaggrok.registered_codes()    # -> [0x10BA, 0x117E, ...]
+diaggrok.parser_info(0x1526)   # -> ParserEntry(name='0x1526', source_type='re', ...)
+```
+
+### Bring your own parsers
+
+You don't have to fork to extend it. Drop a `.py` file that calls `@register(...)` into `~/.diaggrok/plugins/` (or point `DIAGGROK_PLUGIN_DIR` at a directory of them), then:
+
+```python
+diaggrok.load_plugins()
+```
+
+## A note on privacy
+
+Some of these log codes carry personal data, because the modem logs it: NAS and RRC messages can include subscriber and device identifiers, the IMS parsers decode SIP traffic and registration identities, the SIM parsers decode APDUs, and GNSS fixes are your location. diaggrok decodes what's in the record and does not redact anything. If you share decoded output (or the captures themselves), check what's in them first.
+
+## Changes between releases
+
+Releases are tagged `vYYYY.MM.DD`. A parser's record shape is part of the public interface, so [CHANGELOG.md](./CHANGELOG.md) lists every renamed, removed, or re-typed field. `v2026.10.04` has breaking changes to 22 existing parsers (mostly placeholder fields replaced by real decodes, plus `0x4179`, which turned out to be a WCDMA record rather than LTE). Read the changelog before upgrading from `v2026.08.23`.
+
+## Scope, and some honesty
+
+This is carved out of an active reverse-engineering project, so a few things are true and worth saying out loud:
+
+* It only covers modems built on Qualcomm chipsets. Other basebands aren't in scope here.
+* A parser makes it into this repo only once it's been checked against real captures. Plenty of log codes I've looked at aren't here yet, and the ones that are don't all decode every field. Unknown bytes stay as raw values rather than getting a guessed name.
+* 2G/3G is thin — those technologies had been sunset before I got into cellular based tech, and the projects in Kudos below do that far better, so use them for it.
+
+## Kudos
+
+This software is strongly inspired by a few other projects. In many cases they still do a better job parsing logs into usable data. This is especially true for 2G and 3G technologies that had been sunset before I got into cellular based tech. They also have a much longer track record and support ecosystem, so check them out:
+
+* https://osmocom.org/projects/baseband/wiki/Ccch_scan
+* https://github.com/p1sec/qcsuper
+* https://github.com/fgsect/scat
+
+None of the code from these projects is in diaggrok.
+
+## AI Disclaimer
+
+The AI 'bots are VERY good at finding patterns and matching values, exactly what one needs for taking documented output (e.g. AT commands) and matching it up to help you decode a publicly undocumented protocol (e.g. diag logs from a cell modem). If you're opposed to using this kind of work, there are other open source options and some commercial options that you should seek out.
+
+## License
+
+Apache-2.0. See [LICENSE](./LICENSE).

diaggrok-2026.11.8/pyproject.toml

@@ -0,0 +1,47 @@
+[project]
+name = "diaggrok"
+# Single-sourced from src/diaggrok/_version.py: two hand-bumped copies
+# drifted (pyproject 2026.8.5 shipped under public tag v2026.08.23). _version.py
+# is also what the carve stamps into EXTRACT_MANIFEST upstream.diaggrok_version.
+dynamic = ["version"]
+description = "Qualcomm DIAG log code parser library"
+license = "Apache-2.0"
+requires-python = ">=3.11"
+readme = "README.md"
+authors = [{ name = "Luke Jenkins" }]
+keywords = ["diag", "modem", "cellular", "baseband", "lte", "5g"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Science/Research",
+    "Intended Audience :: Telecommunications Industry",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Communications",
+    "Topic :: System :: Hardware",
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/lukejenkins/diaggrok"
+Source = "https://github.com/lukejenkins/diaggrok"
+Changelog = "https://github.com/lukejenkins/diaggrok/releases"
+
+[build-system]
+requires = ["setuptools>=77.0"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.dynamic]
+version = {attr = "diaggrok._version.__version__"}
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["src"]

diaggrok-2026.11.8/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

diaggrok-2026.11.8/src/diaggrok/__init__.py

@@ -0,0 +1,58 @@
+"""diaggrok — DIAG log code parser library."""
+from diaggrok._version import __version__
+from diaggrok.frame import parse_outer_frame
+from diaggrok.registry import (
+    Canary,
+    FieldGround,
+    GROUND_TRUTH_STATUSES,
+    GroundTruth,
+    SOURCE_KINDS,
+    SOURCE_TYPES,
+    Source,
+    TEST_MODES,
+    TIMEBASE_ROLES,
+    VALIDATION_STATES,
+    ParserEntry,
+    WIGLE_DIRECT_ROLES,
+    WIGLE_INDIRECT_ROLES,
+    WIGLE_TIMING_SUBFLAGS,
+    all_parser_info,
+    clear_registry,
+    entries_for,
+    load_plugins,
+    parse,
+    parser_info,
+    register,
+    registered_codes,
+    resolve,
+)
+
+__all__ = [
+    "__version__",
+    "Canary",
+    "FieldGround",
+    "GROUND_TRUTH_STATUSES",
+    "GroundTruth",
+    "SOURCE_KINDS",
+    "SOURCE_TYPES",
+    "Source",
+    "TEST_MODES",
+    "TIMEBASE_ROLES",
+    "VALIDATION_STATES",
+    "ParserEntry",
+    "WIGLE_DIRECT_ROLES",
+    "WIGLE_INDIRECT_ROLES",
+    "WIGLE_TIMING_SUBFLAGS",
+    "all_parser_info",
+    "clear_registry",
+    "entries_for",
+    "load_plugins",
+    "parse",
+    "parse_outer_frame",
+    "parser_info",
+    "register",
+    "registered_codes",
+    "resolve",
+]
+
+import diaggrok.parsers  # noqa: E402, F401 — trigger built-in parser registration

diaggrok-2026.11.8/src/diaggrok/_version.py

@@ -0,0 +1 @@
+__version__ = '2026.11.8'