VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

bikeshed: vulnerability history, versions and safety

bikeshed is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 0 release, first recorded in Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bikeshed vulnerabilities

Vulert verdict on bikeshed 7.2.0 i

Updated on 23 Oct 2026

Good news: 7.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 81/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 7.2.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 30 Aug 2021 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Stars 1,330 i
  • Last release this month i
  • Licence non-standard 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.

01 Versions

Which versions are affected

Every version Vulert tracks for bikeshed, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.2.0 13 Oct 2026 none non-standard — Details →
7.1.3 18 Sep 2026 none non-standard — Details →
7.1.2 21 Aug 2026 none non-standard — Details →
7.1.1 09 Jun 2026 none non-standard — Details →
7.1.0 09 Jun 2026 none non-standard — Details →
7.0.14 05 Jun 2026 none non-standard — Details →
7.0.13 04 Jun 2026 none non-standard — Details →
7.0.12 03 Jun 2026 none non-standard — Details →
7.0.11 04 May 2026 none non-standard — Details →
7.0.10 17 Apr 2026 none non-standard — Details →
7.0.9 16 Apr 2026 none non-standard — Details →
7.0.8 16 Apr 2026 none non-standard — Details →
7.0.7 06 Jan 2026 none non-standard — Details →
7.0.6 22 Dec 2025 none non-standard — Details →
7.0.5 15 Dec 2025 none non-standard — Details →
7.0.4 12 Dec 2025 none non-standard — Details →
7.0.3 12 Dec 2025 none non-standard — Details →
7.0.2 10 Dec 2025 none non-standard — Details →
7.0.1 08 Dec 2025 none non-standard — Details →
7.0.0 05 Dec 2025 none non-standard — Details →
6.1.1 05 Dec 2025 none non-standard — Details →
6.1.0 05 Dec 2025 none non-standard — Details →
6.0.0 04 Dec 2025 none non-standard — Details →
5.4.2 27 Nov 2025 none non-standard — Details →
5.4.1 18 Nov 2025 none non-standard — Details →
5.4.0 10 Nov 2025 none non-standard — Details →
5.3.6 05 Nov 2025 none non-standard — Details →
5.3.5 04 Nov 2025 none non-standard — Details →
5.3.4 28 Jul 2025 none non-standard — Details →
5.3.3 14 Jul 2025 none non-standard — Details →
5.3.2 27 Jun 2025 none non-standard — Details →
5.3.1 26 Jun 2025 none non-standard — Details →
5.3.0 26 Jun 2025 none non-standard — Details →
5.2.1 11 Jun 2025 none non-standard — Details →
5.2.0 27 May 2025 none non-standard — Details →
5.1.2 14 Mar 2025 none non-standard — Details →
5.1.1 06 Mar 2025 none non-standard — Details →
5.1.0 21 Feb 2025 none non-standard — Details →
5.0.6 19 Feb 2025 none non-standard — Details →
5.0.5 18 Feb 2025 none non-standard — Details →
5.0.4 14 Feb 2025 none non-standard — Details →
5.0.3 04 Feb 2025 none non-standard — Details →
5.0.2 31 Jan 2025 none non-standard — Details →
5.0.1 31 Jan 2025 none non-standard — Details →
5.0.0 17 Jan 2025 none non-standard — Details →
4.2.8 06 Dec 2024 none non-standard — Details →
3.14.6 21 Nov 2024 none CC0-1.0 — Details →
4.2.7 04 Nov 2024 none non-standard — Details →
4.2.6 04 Nov 2024 none non-standard — Details →
4.2.5 04 Nov 2024 none non-standard — Details →
4.2.4 04 Nov 2024 none non-standard — Details →
4.2.3 28 Oct 2024 none non-standard — Details →
4.2.2 28 Oct 2024 none non-standard — Details →
4.2.1 21 Oct 2024 none non-standard — Details →
4.2.0 15 Oct 2024 none non-standard — Details →
4.1.12 06 Aug 2024 none non-standard — Details →
4.1.11 06 Aug 2024 none non-standard — Details →
4.1.10 24 Jul 2024 none non-standard — Details →
4.1.9 17 Jun 2024 none non-standard — Details →
4.1.8 28 May 2024 none non-standard — Details →
4.1.7 28 May 2024 none non-standard — Details →
4.1.6 08 Mar 2024 none non-standard — Details →
4.1.5 27 Jan 2024 none non-standard — Details →
4.1.4 26 Jan 2024 none non-standard — Details →
4.1.3 25 Jan 2024 none non-standard — Details →
4.1.2 24 Jan 2024 none non-standard — Details →
4.1.1 24 Jan 2024 none non-standard — Details →
4.1.0 02 Jan 2024 none non-standard — Details →
4.0.3 18 Dec 2023 none non-standard — Details →
4.0.2 14 Dec 2023 none non-standard — Details →
4.0.1 12 Dec 2023 none non-standard — Details →
4.0.0 08 Dec 2023 none non-standard — Details →
3.14.5 08 Sep 2023 none CC0-1.0 — Details →
3.14.4 17 Aug 2023 none CC0-1.0 — Details →
3.14.3 19 Jul 2023 none CC0-1.0 — Details →
3.14.2 19 Jul 2023 none CC0-1.0 — Details →
3.14.1 18 Jul 2023 none CC0-1.0 — Details →
3.14.0 11 Jul 2023 none CC0-1.0 — Details →
3.13.1 22 Jun 2023 none CC0-1.0 — Details →
3.13.0 20 Jun 2023 none CC0-1.0 — Details →
3.12.1 30 May 2023 none CC0-1.0 — Details →
3.12.0 30 May 2023 none CC0-1.0 — Details →
3.11.23 28 Apr 2023 none CC0-1.0 — Details →
3.11.22 19 Apr 2023 none CC0-1.0 — Details →
3.11.21 23 Mar 2023 none CC0-1.0 — Details →
3.11.20 23 Mar 2023 none CC0-1.0 — Details →
3.11.19 23 Mar 2023 none CC0-1.0 — Details →
3.11.18 22 Mar 2023 none CC0-1.0 — Details →
3.11.17 21 Mar 2023 none CC0-1.0 — Details →
3.11.16 10 Mar 2023 none CC0-1.0 — Details →
3.11.14 10 Mar 2023 none CC0-1.0 — Details →
3.11.13 02 Mar 2023 none CC0-1.0 — Details →
3.11.12 28 Feb 2023 none CC0-1.0 — Details →
3.11.11 28 Feb 2023 none CC0-1.0 — Details →
3.11.10 17 Feb 2023 none CC0-1.0 — Details →
3.11.9 16 Feb 2023 none CC0-1.0 — Details →
3.11.8 16 Feb 2023 none CC0-1.0 — Details →
3.11.7 16 Feb 2023 none CC0-1.0 — Details →
3.11.6 15 Feb 2023 none CC0-1.0 — Details →
3.11.5 14 Feb 2023 none CC0-1.0 — Details →
3.11.4 28 Jan 2023 none — — Details →
3.11.3 27 Jan 2023 none — — Details →
3.11.2 27 Jan 2023 none — — Details →
3.11.1 17 Jan 2023 none — — Details →
3.11.0 13 Jan 2023 none — — Details →
3.10.1 09 Dec 2022 none — — Details →
3.10.0 25 Oct 2022 none — — Details →
3.9.0 21 Oct 2022 none — — Details →
3.8.2 13 Oct 2022 none — — Details →
3.8.1 12 Oct 2022 none — — Details →
3.8.0 11 Oct 2022 none — — Details →
3.7.7 11 Oct 2022 none — — Details →
3.7.6 08 Oct 2022 none — — Details →
3.7.5 07 Oct 2022 none — — Details →
3.7.4 30 Jul 2022 none — — Details →
3.7.3 27 Jul 2022 none — — Details →
3.7.2 27 Jul 2022 none — — Details →
3.7.1 15 Jul 2022 none — — Details →
3.7.0 27 May 2022 none — — Details →
3.6.0 27 May 2022 none — — Details →

The newest 120 of 187 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for bikeshed

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-23422: OS Command Injection in bikeshed 7.8 high 3.0.0 30 Aug 2021
CVE-2021-23423: Path Traversal in bikeshed 5.5 medium 3.0.0 30 Aug 2021
CVE-2021-23422: bikeshed Package Command Injection N/A unrated b2f668fca204260b1cad28d5078e93471cb6b2dd 16 Aug 2021
CVE-2021-23423: bikeshed Package HTML Output Disclosure N/A unrated b2f668fca204260b1cad28d5078e93471cb6b2dd 16 Aug 2021

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 bikeshed

Is bikeshed safe to use?

Vulert records 4 vulnerabilities for bikeshed in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is bikeshed's Vulert package health score?

Vulert scores bikeshed 81/100, which reads as in good shape. 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 bikeshed affected?

No. 7.2.0, 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 bikeshed should I use?

7.2.0 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 bikeshed have?

4 vulnerabilities are recorded for bikeshed in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new bikeshed vulnerabilities disclosed?

0 vulnerabilities were recorded for bikeshed in the last 12 months, and the oldest entry in this database dates to 16 Aug 2021. 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 bikeshed 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 bikeshed for upcoming vulnerabilities?

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