PAGES
← all tools
◆ Hacking Hardware

Packetry

v0.5.0 open-source

Free plan: not checked yet · Open source: yes

Packetry is a fast, intuitive USB 2.0 protocol analysis application for use with Cynthion.

What you can do now

Checking Plays…

Summary

Packetry is an open-source desktop application for capturing and inspecting USB 2.0 traffic, built to work with the Cynthion hardware analyzer rather than as a standalone sniffer. It runs as a GTKGTKA cross-platform widget toolkit maintained by the GNOME project for building graphical user interfaces in C, with bindings for many languages, giving cyber tools a native desktop UI without writing platform-specific rendering code. 4 application built from source with Rust and Cargo, loading .pcap files with USB 2.0 link-layer headers for offline review or displaying live captures from a connected Cynthion device. That hardware pairing makes it a fit for hardware hackers, embedded developers, and USB researchers who need protocol-level visibility during device development or reverse engineering, rather than for general network security teams. Cynthion's own documentation describes Packetry as the open-source analysis software that complements its FPGA-based USB protocol analyzer, so the two are meant to be evaluated together rather than as separate purchases. The project dates to 2022 and remains under active development, with documentation and a public GitHub repository tracking issues and releases.

Packetry is a fast, intuitive USB 2.0 protocol analysis application for use with Cynthion.

How Packetry helps

What is my USB device actually sending back and forth with the host?

shows a live or captured trace of every transaction on the bus, decoded down to the link layer, so the exchange between host and device is visible transaction by transaction

Where in the enumeration or transfer sequence did my device stop behaving correctly?

lets you step through a capture in order and inspect each packet's fields, so the point where the traffic diverges from what the device should be doing is visible directly in the trace

Can I diagnose a USB issue after the fact without the hardware attached?

loads a previously saved capture file recorded with the USB 2.0 link layer header, so the same inspection works offline on a trace taken earlier

Is a particular USB transfer type or speed behaving as expected on this device?

breaks a capture down by transaction so Low-, Full-, and High-Speed traffic recorded from the device can be reviewed at the protocol level rather than as raw bytes

all 9 features, with the evidence for each →

Languages

Not documented

Features

9 capabilities

Built from Packetry's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Packetry offers you

  • Command-line interface1
All capabilities 9 capabilities
USB traffic capture and inspection shipped Captures and inspects USB 2.0 protocol traffic using Cynthion hardware. 3 other sources · first seen Aug 2024

docs

  • USB 2.0 protocol analysis application for capturing and inspecting USB traffic, designed for use with Cynthion hardware.

example

  • View expanded packet information in the new detail pane of the GUI. Use the 'detail pane' view in the UI v0.2.0 · Aug 2024 · source
  • Install the portable Linux desktop build as a single executable binary. ./packetry.AppImage v0.2.0 · Aug 2024 · source
HID report descriptor decoding shipped Adds capability to decode Human Interface Device (HID) report descriptors during traffic analysis. 2 releases · first seen Sep 2024

release

Packetry CLI wrapper support shipped Provides a command-line interface wrapper program for Packetry commands, including specific support for Windows environments. 1 release · 1 other source · first seen Aug 2024

Also counts toward: Command-line interface

release

  • Add packetry-cli wrapper program, enabling command-line options on Windows. v0.2.0 · Aug 2024 · source · release history

example

  • Run Packetry commands via CLI on Windows using the new wrapper. packetry-cli <args> v0.2.0 · Aug 2024 · source
Capture database dump utility shipped Provides a facility to dump the internal capture database, primarily for debugging purposes. 1 release · first seen Sep 2025

release

  • Add facility to dump the capture database for debugging. v0.5.0 · Sep 2025 · source · release history
Non-packet event support shipped Adds support for capturing and handling non-packet events from the Cynthion analyzer. 1 release · first seen Sep 2025

release

  • Add support for non-packet events from Cynthion analyzer. v0.5.0 · Sep 2025 · source · release history
PcapNG export with custom blocks shipped Supports exporting capture data in PcapNG format, including the ability to include custom non-packet blocks. 1 release · first seen Sep 2025

release

  • Add support for the PcapNG file format with custom non-packet blocks. v0.5.0 · Sep 2025 · source · release history
VBUS power control shipped Enables control of VBUS power output via the Cynthion analyzer hardware. 1 release · first seen Sep 2025

release

  • Add support for VBUS power control with Cynthion analyzer. v0.5.0 · Sep 2025 · source · release history
Transaction and packet capture views shipped Offers both transaction-level and packet-level perspectives for analyzing captured USB traffic. 1 release · first seen Oct 2024

release

  • Adds transaction-level and packet-level views of capture v0.3.0 · Oct 2024 · source · release history
USB capture device backend API shipped Exposes a backend API interface for interacting with USB capture devices. 1 release · first seen Oct 2024

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Packetry, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Packetry puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

4 entries

  1. September 20251
  2. October 20241
  3. September 20241
  4. August 20241

    4 entries

    Project health

    Issue, contributor and maintainer activity in greatscottgadgets/packetry, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 5 +1 vs prior 12 months
    2. Maintainers 2 +2 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 60% of issues opened, last 12 months
    5. Median time to close 79 days first maintainer reply 0.9 hours
    6. Open backlog 14 of 74 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 14
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.