ChipWhisperer
v6.0.0b open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on ChipWhisperer's page any more, so we've brought you to the top.
The complete open-source toolchain for side-channel power analysis and glitching attacks.
scope.vglitch_reset()
scope.io.nrst_drive_poweroff = True
import chipwhisperer as cw
from chipwhisperer.capture.targets.Traces import IndividualIterable
# Assuming 'traces' is an instance of IndividualIterable
trace_array = np.array(traces)
sn = scope.sn
print(f'Connected device SN: {sn}')
cw.plot(analysis_results)
import chipwhisperer as cw
cw.log.set_level('scope', 'DEBUG')
cw.log.set_level('naeusb', 'WARNING')
import chipwhisperer as cw
cw.correlation_vs_trace(traces, key_guesses)
import chipwhisperer as cw
scope = cw.scope()
print(scope.fw_version_str)
import chipwhisperer as cw
scope = cw.scope()
traces = scope.get_last_trace(as_int=True)
What you can do now
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
Languages
Command line
| 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 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 → 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 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…
Releases
18 entries
No entries match these filters.
- March 20251
- January 202517
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.
- Contributors 5 −8 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 7.2 days first maintainer reply 7.2 days
- Open backlog 39 of 406 issues ever filed
- Issues opened / month 3 · 0 communitymaintainers
- Open backlog 39
- Contributors / month 0
- Commits / month 0
- Stars not measured
- 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.