Vulnerability Database · PyPI · Package report

wavedrom: vulnerability history, versions and safety

Q: How do I monitor wavedrom for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the wavedrom version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

wavedrom is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wavedrom vulnerabilities

Vulert verdict on wavedrom 2.0.3.post3 i

Updated on 23 Oct 2026

Good news: 2.0.3.post3, the version you would install today, has no known vulnerabilities.

Package health score 50/100

Security Minor issues
Maintenance Unmaintained
Popularity Niche
Community Inactive

What to do: Stay on 2.0.3.post3 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.3.post3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 2.0.3.post3 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 76 packages i
Stars 118 i
OpenSSF scorecard 1/10 i
Last release 52 months ago i
Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for wavedrom, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
2.0.3.post3	27 May 2022	none	MIT	—	Details →
2.0.3.post2	12 Sep 2019	none	MIT	—	Details →
2.0.3.post1	05 Sep 2019	none	MIT	—	Details →
2.0.3	30 Aug 2019	none	MIT	—	Details →
2.0.2	30 Aug 2019	none	MIT	—	Details →
1.8.0.post4	25 May 2019	none	MIT	—	Details →
1.8.0.post3	21 May 2019	none	MIT	—	Details →
1.9.0rc1	21 Apr 2019	none	MIT	—	Details →
1.8.0.post2	18 Apr 2019	none	MIT	—	Details →
1.8.0.post1	17 Apr 2019	none	MIT	—	Details →
1.8.0	16 Apr 2019	none	MIT	—	Details →
1.8.0rc3	27 Nov 2018	none	MIT	—	Details →
1.8.0rc2	27 Nov 2018	none	MIT	—	Details →
1.8.0rc1	27 Nov 2018	none	MIT	—	Details →
0.1.0	20 Nov 2018	none	MIT	—	Details →
0.0.7	16 Nov 2018	none	MIT	—	Details →
0.0.6	16 Nov 2018	none	MIT	—	Details →

All 17 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for wavedrom

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

About wavedrom

Is wavedrom safe to use?

Vulert has no vulnerabilities on record for wavedrom in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is wavedrom's Vulert package health score?

Vulert scores wavedrom 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of wavedrom affected?

No. 2.0.3.post3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of wavedrom should I use?

2.0.3.post3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does wavedrom have?

0 vulnerabilities are recorded for wavedrom in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wavedrom vulnerabilities disclosed?

0 vulnerabilities were recorded for wavedrom in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wavedrom are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wavedrom for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wavedrom version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.