PAGES
← all tools
◆ Hacking Hardware

ChipWhisperer

v6.0.0b open-source

Free plan: not checked yet · Open source: yes

The complete open-source toolchain for side-channel power analysis and glitching attacks.

What you can do now

Checking Plays…

Summary

ChipWhisperer is an open-source toolchain for hardware security research, covering side-channel power analysis and fault injection against embedded targets. It combines capture and target hardware boards with open firmware and a Python API, ChipWhisperer Capture and Analyzer, that's imported into scripts to configure the hardware, run captures, and process power traces, so it's used as a library rather than a standalone application. It suits hardware security researchers and embedded engineers testing devices for glitching and power-analysis vulnerabilities rather than software-only security teams. Launched in 2014, it remains under active development with maintained documentation, tutorials, and a support community.

The complete open-source toolchain for side-channel power analysis and glitching attacks.

How ChipWhisperer helps

Where in a target's power trace does a secret-dependent operation actually leak?

captures power measurements synchronized to the target's execution and lets the Python API align and process the traces to pinpoint where signal correlates with a key-dependent operation

Is a device's cryptographic implementation vulnerable to a power-analysis attack?

runs captured traces through ChipWhisperer Analyzer's correlation and analysis routines to recover key material, giving a concrete pass/fail on whether the leakage is exploitable

Can a voltage or clock glitch cause this embedded target to skip a security check?

drives the capture board's fault-injection hardware to inject glitches at chosen timings and reports which offsets flip the target's behavior, such as bypassing a check

How reproducible is a capture-and-attack sequence across many runs or targets?

since the boards and captures are driven from a Python script rather than a GUI, the same configuration, capture, and analysis steps can be replayed and scripted against multiple targets or trials

What does the live state of the attached capture and target hardware look like right now?

the scope object returned by the API reports current settings such as gain and trigger state, letting a script or researcher confirm the hardware is configured as expected before a capture run

all 8 features, with the evidence for each →

Languages

Not documented

Features

8 capabilities

Built from ChipWhisperer'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 →

  • ChipWhisperer covers 1 of the 5 supply chain security capabilities we track.

What ChipWhisperer offers you

  • Python scripting support2
  • Scripting API2
  • Scripting language support2
  • Command-line interface
All capabilities 8 capabilities
Fault injection attacks shipped Provides Python APIs for performing fault injection attacks on embedded targets. 8 releases · 2 other sources · first seen Jan 2025

Also counts toward: Python scripting support, Scripting API, Scripting language support

release 8 total

docs

  • Open source toolchain for hardware security research, providing Python APIs for power analysis and fault injection attacks on embedded targets.

example

  • Reset the voltage glitch controller state on the capture board. scope.vglitch_reset() v6.0.0b · Mar 2025 · source
SimpleSerial protocol enhancements shipped Adds support for SimpleSerialV2 protocol and helper functions for last sent/read operations and error handling. 10 releases · first seen Jan 2025

release 10 total

  • XON/XOFF flow control is now available for serial communications v6.0.0b · Mar 2025 · source · release history
  • FPGAs now support SSV2 protocol v6.0.0b · Mar 2025 · source · release history
  • scope.io.nrst_drive_poweroff controls nRST pin behavior when target_pwr=False v6.0.0b · Mar 2025 · source · release history
  • Adds SimpleSerial helper function simpleserial_last_sent 5.2.1 · Jan 2025 · source · release history
  • Adds SimpleSerial helper function simpleserial_read_witherrors 5.2.1 · Jan 2025 · source · release history
  • Adds SimpleSerial helper function simpleserial_last_read 5.2.1 · Jan 2025 · source · release history
Extended hardware target support shipped Adds firmware targets and programming support for STM32, FE310, PSoC62, and additional SAMFWLoader capabilities. 7 releases · 1 other source · first seen Jan 2025

release 7 total

  • Husky-Plus hardware is now supported v6.0.0b · Mar 2025 · source · release history
  • Capture module adds STM32 programmer target for STM32 microcontrollers. 3.5.0 · Jan 2025 · source · release history
  • Add openocd/fe310.cfg to allow fe310 programming via MPSSE 5.7.0 · Jan 2025 · source · release history
  • Add openocd/run_openocd.sh for easier JTAG/SWD programming and debugging 5.7.0 · Jan 2025 · source · release history
  • Add SAM4S bootloader support - allows programming SAM4S target boards 5.7.0 · Jan 2025 · source · release history
  • Capture module adds SPI flash programmer target for programming SPI flash devices. 3.5.0 · Jan 2025 · source · release history

example

  • Configure specific logging levels for ChipWhisperer subsystems using the new multi-logger system. import chipwhisperer as cw cw.log.set_level('scope', 'DEBUG') cw.log.set_level('naeusb', 'WARNING') 5.5.1 · Jan 2025 · source
Real-time capture and multi-device support shipped Enables simultaneous connection to multiple scopes, streaming mode for real-time data handling, and batch capture acceleration. 6 releases · 2 other sources · first seen Jan 2025

release

  • Adds basic support for multiple channels in the Capture module 3.2.0 · Jan 2025 · source · release history
  • Capture module now supports connecting multiple CW-Lite or CW-Pro scopes simultaneously. 3.5.0 · Jan 2025 · source · release history
  • Adds batch run capability for CW305 to accelerate capture 5.3.0 · Jan 2025 · source · release history
  • Adds a new Streaming mode capture option to the Capture module for real-time data handling 3.2.0 · Jan 2025 · source · release history
  • Add scope.fw_version_str to expose firmware version string 5.6.1 · Jan 2025 · source · release history
  • Add segmented capture to ChipWhisperer for super fast capture 5.5 · Jan 2025 · source · release history

example

  • Check the firmware version string of the connected scope without parsing logs. import chipwhisperer as cw scope = cw.scope() print(scope.fw_version_str) 5.6.1 · Jan 2025 · source
  • Retrieve the serial number of the connected ChipWhisperer hardware programmatically. sn = scope.sn print(f'Connected device SN: {sn}') 5.4 · Jan 2025 · source
Power analysis attacks shipped Provides Python APIs for capturing and analysing power traces to perform side-channel attacks on embedded targets. 6 releases · 1 other source · first seen Jan 2025

Also counts toward: Python scripting support, Scripting API, Scripting language support

release

  • Adds support for the NXP Cross-over MCU RT1062 via a new HAL target 5.2.1 · Jan 2025 · source · release history
  • Adds FW MBED TLS crypto library support for ARM targets 3.5.3 · Jan 2025 · source · release history
  • Adds STM32F firmware targets (STM32F0, F1, F2, F3, F4) for chip targeting 3.4.0 · Jan 2025 · source · release history
  • Adds PSOC62 HAL support alongside fixes for NRF52840 and SAM4L HALs 5.1.3 · Jan 2025 · source · release history
  • Adds option for more specific hardware AES engine triggers 5.2.1 · Jan 2025 · source · release history
  • Trace recorder feature added for capturing traces 3.1.8 · Jan 2025 · source · release history

docs

  • Open source toolchain for hardware security research, providing Python APIs for power analysis and fault injection attacks on embedded targets.
Automated analysis and plotting shipped Provides automated functions for visualizing trace analysis results and converting captured traces into numerical formats for easier processing. 4 releases · 2 other sources · first seen Jan 2025

release

  • Adds __array__() method to IndividualIterable to enable numpy conversion 5.3.0 · Jan 2025 · source · release history
  • Adds cw.plot() function for automated plotting of analyzer outputs 5.4 · Jan 2025 · source · release history
  • Adds automated plotting functions for analyzer plots 5.4 · Jan 2025 · source · release history
  • Faster graph plotting performance, especially in fast mode 3.1.8 · Jan 2025 · source · release history

example

  • Convert captured traces directly into a numpy array for analysis without intermediate steps. import chipwhisperer as cw from chipwhisperer.capture.targets.Traces import IndividualIterable # Assuming 'traces' is an instance of IndividualIterable trace_array = np.array(traces) 5.3.0 · Jan 2025 · source
  • Use the new automated plotting function to visualize trace analysis results directly. cw.plot(analysis_results) 5.4 · Jan 2025 · source
Advanced SCA attack algorithms shipped Implements specific cryptographic attack capabilities including DES key recovery, AES MixColumns with Variable Vector KTP, and dynamic trace resynchronization. 4 releases · first seen Jan 2025

Shared capability: Dependency scanning

release

  • Adds support for T-Table enc/dec leakage models 5.3.0 · Jan 2025 · source · release history
  • Adds DES key recovery capability in the Analyzer module (recovers 48 of 56 bits) 3.2.0 · Jan 2025 · source · release history
  • Adds Dynamic Time Warp (DTW) based trace resync preprocessing using the Elastic Alignment paper by Jasper van Woudenberg et al 3.4.0 · Jan 2025 · source · release history
  • Adds AES MixColumns attack capability with Variable Vector KTP (requires scared/estraces) 5.4 · Jan 2025 · source · release history
Glitch trace analysis shipped Provides tools and interfaces for analyzing glitch traces, including a dedicated widget and integration with the analyzer. 1 release · first seen Jan 2025

release

  • glitch_explorer widget introduced for analyzing glitch traces. 3.1.9 · Jan 2025 · source · release history

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 ChipWhisperer, 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 ChipWhisperer 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

Show

18 entries

  1. March 20251
  2. January 202517
    Show

    18 entries

    Project health

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

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

    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.