Vulnerability Database · PyPI · Package report
ua-parser-builtins: vulnerability history, versions and safety
ua-parser-builtins is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on ua-parser-builtins 202610.0.0 i
Updated on 23 Oct 2026
Good news: 202610.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on 202610.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 202610.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 202610.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 783 packages i
- Stars 648 i
- OpenSSF scorecard 5/10 i
- Last release this month i
- Licence Apache-2.0 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 ua-parser-builtins, 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.
- 202610.0.0 02 Oct 2026
- 202606.0.0 01 Jun 2026
- 202605.0.0 01 May 2026
- 202603.0.0 01 Mar 2026
- 202602.0.0 02 Feb 2026
- 202601.0.0 02 Jan 2026
- 0.19.0.dev79 01 Aug 2025
- 0.19.0.dev78 01 Jul 2025
- 0.19.0.dev66 01 Apr 2025
- 0.19.0.dev62 03 Mar 2025
- 0.19.0.dev39 01 Feb 2025
- 0.18.0.post1 05 Dec 2024
- 0.16.0.post1 05 Dec 2024
- 0.15.0.post1 05 Dec 2024
- 0.18.0 26 Nov 2024
- 0.15.0 26 Nov 2024
- 0.16.0 26 Nov 2024
- 0.19.0.dev30 26 Nov 2024
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 202610.0.0 | 02 Oct 2026 | none | Apache-2.0 | — | Details → |
| 202606.0.0 | 01 Jun 2026 | none | Apache-2.0 | — | Details → |
| 202605.0.0 | 01 May 2026 | none | Apache-2.0 | — | Details → |
| 202603.0.0 | 01 Mar 2026 | none | Apache-2.0 | — | Details → |
| 202602.0.0 | 02 Feb 2026 | none | Apache-2.0 | — | Details → |
| 202601.0.0 | 02 Jan 2026 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev79 | 01 Aug 2025 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev78 | 01 Jul 2025 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev66 | 01 Apr 2025 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev62 | 03 Mar 2025 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev39 | 01 Feb 2025 | none | Apache-2.0 | — | Details → |
| 0.18.0.post1 | 05 Dec 2024 | none | Apache-2.0 | — | Details → |
| 0.16.0.post1 | 05 Dec 2024 | none | Apache-2.0 | — | Details → |
| 0.15.0.post1 | 05 Dec 2024 | none | Apache-2.0 | — | Details → |
| 0.18.0 | 26 Nov 2024 | none | Apache-2.0 | — | Details → |
| 0.15.0 | 26 Nov 2024 | none | Apache-2.0 | — | Details → |
| 0.16.0 | 26 Nov 2024 | none | Apache-2.0 | — | Details → |
| 0.19.0.dev30 | 26 Nov 2024 | none | Apache-2.0 | — | Details → |
All 18 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.
03 Vulnerabilities
Recorded vulnerabilities for ua-parser-builtins
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
Questions
About ua-parser-builtins
Is ua-parser-builtins safe to use?
Vulert has no vulnerabilities on record for ua-parser-builtins 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 ua-parser-builtins's Vulert package health score?
Vulert scores ua-parser-builtins 84/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 ua-parser-builtins affected?
No. 202610.0.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 ua-parser-builtins should I use?
202610.0.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 ua-parser-builtins have?
0 vulnerabilities are recorded for ua-parser-builtins 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 ua-parser-builtins vulnerabilities disclosed?
0 vulnerabilities were recorded for ua-parser-builtins 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 ua-parser-builtins 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 ua-parser-builtins for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ua-parser-builtins version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.