Vulnerability Database · PyPI · Package report

blis: vulnerability history, versions and safety

Q: How do I monitor blis for upcoming vulnerabilities?

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

blis 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 blis vulnerabilities

Vulert verdict on blis 1.3.3 i

Updated on 23 Oct 2026

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

Package health score 76/100

Security Minor issues
Maintenance Sustainable
Popularity Widely used
Community Quiet

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

Current release 1.3.3 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 2,555 packages i
Stars 239 i
OpenSSF scorecard 4/10 i
Last release 11 months ago 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for blis, 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
1.3.3	17 Nov 2025	none	non-standard	—	Details →
1.3.2	12 Nov 2025	none	non-standard	—	Details →
1.3.1	12 Nov 2025	none	non-standard	—	Details →
1.3.0	03 Apr 2025	none	non-standard	—	Details →
1.2.1	01 Apr 2025	none	non-standard	—	Details →
1.2.0	13 Jan 2025	none	non-standard	—	Details →
0.8.0	12 Jan 2025	none	non-standard	—	Details →
1.1.0	16 Dec 2024	none	BSD-3-Clause	—	Details →
1.1.0a0	12 Dec 2024	none	BSD-3-Clause	—	Details →
1.0.2	10 Dec 2024	none	BSD-3-Clause	—	Details →
1.0.1	13 Sep 2024	none	BSD-3-Clause	—	Details →
1.0.0	27 Jul 2024	none	BSD-3-Clause	—	Details →
1.0.0a1	25 Jul 2024	none	BSD-3-Clause	—	Details →
0.7.11	22 Sep 2023	none	non-standard	—	Details →
0.7.10	21 Jul 2023	none	non-standard	—	Details →
0.7.9	16 Oct 2022	none	non-standard	—	Details →
0.9.1	04 Aug 2022	none	non-standard	—	Details →
0.9.1.dev1	02 Aug 2022	none	non-standard	—	Details →
0.9.1.dev0	26 Jul 2022	none	non-standard	—	Details →
0.7.8	22 Jun 2022	none	non-standard	—	Details →
0.9.0	10 May 2022	none	non-standard	—	Details →
0.7.7	22 Mar 2022	none	non-standard	—	Details →
0.7.6	15 Feb 2022	none	non-standard	—	Details →
0.7.5	22 Oct 2021	none	non-standard	—	Details →
0.7.4	07 Dec 2020	none	non-standard	—	Details →
0.7.3	23 Nov 2020	none	non-standard	—	Details →
0.7.2	03 Nov 2020	none	non-standard	—	Details →
0.7.1	16 Aug 2020	none	non-standard	—	Details →
0.7.1.dev0	15 Aug 2020	none	non-standard	—	Details →
0.7.0	15 Aug 2020	none	non-standard	—	Details →
0.4.1	14 Nov 2019	none	non-standard	—	Details →
0.4.0	23 Aug 2019	none	non-standard	—	Details →
0.4.0.dev1	23 Aug 2019	none	non-standard	—	Details →
0.4.0.dev0	23 Aug 2019	none	non-standard	—	Details →
0.3.1	18 Aug 2019	none	non-standard	—	Details →
0.2.4	08 Mar 2019	none	MIT	—	Details →
0.2.3	27 Feb 2019	none	MIT	—	Details →
0.2.3.dev3	27 Feb 2019	none	MIT	—	Details →
0.2.3.dev2	25 Feb 2019	none	MIT	—	Details →
0.2.3.dev1	25 Feb 2019	none	MIT	—	Details →
0.2.3.dev0	25 Feb 2019	none	MIT	—	Details →
0.2.2	26 Nov 2018	none	MIT	—	Details →
0.2.2.dev0	25 Nov 2018	none	MIT	—	Details →
0.2.1	25 Nov 2018	none	MIT	—	Details →
0.2.0	10 Nov 2018	none	MIT	—	Details →
0.2.0.dev0	10 Nov 2018	none	MIT	—	Details →
0.1.0	23 Oct 2018	none	MIT	—	Details →
0.0.16	23 Oct 2018	none	MIT	—	Details →
0.0.13	13 Oct 2017	none	MIT	—	Details →
0.0.12	12 Oct 2017	none	MIT	—	Details →
0.0.10	12 Oct 2017	none	—	—	Details →
0.0.9.dev104	11 Oct 2017	none	—	—	Details →
0.0.8	11 Oct 2017	none	MIT	—	Details →
0.0.6	10 Sep 2016	none	MIT	—	Details →
0.0.5	10 Sep 2016	none	MIT	—	Details →
0.0.4	10 Aug 2016	none	MIT	—	Details →
0.0.3	31 Jul 2016	none	MIT	—	Details →
0.0.2	28 Jul 2016	none	MIT	—	Details →
0.0.1	28 Jul 2016	none	MIT	—	Details →

All 59 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 blis

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 blis

Is blis safe to use?

Vulert has no vulnerabilities on record for blis 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 blis's Vulert package health score?

Vulert scores blis 76/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 blis affected?

No. 1.3.3, 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 blis should I use?

1.3.3 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 blis have?

0 vulnerabilities are recorded for blis 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 blis vulnerabilities disclosed?

0 vulnerabilities were recorded for blis 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 blis 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 blis for upcoming vulnerabilities?

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