Packetry
v0.5.0 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on Packetry's page any more, so we've brought you to the top.
Packetry is a fast, intuitive USB 2.0 protocol analysis application for use with Cynthion.
packetry-cli <args> ./packetry.AppImage
What you can do now
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Releases
4 entries
No entries match these filters.
- September 20251
- October 20241
- September 20241
- August 20241
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.
- Contributors 5 +1 vs prior 12 months
- Maintainers 2 +2 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 60% of issues opened, last 12 months
- Median time to close 79 days first maintainer reply 0.9 hours
- Open backlog 14 of 74 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 14
- Contributors / month 0
- Commits / month 0
- Stars not measured
- 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.