Vulnerability Database · Pub · Package report
pubspec_parse: vulnerability history, versions and safety
pubspec_parse is a package in the Pub ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Pub ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on pubspec_parse 1.7.0 i
Updated on 23 Oct 2026
Good news: 1.7.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Not enough data
- Community Not enough data
What to do: Stay on 1.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.7.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release this month i
Version list, release dates, licence and dependants published by pub.dev, 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 pubspec_parse, 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.
- 1.7.0 21 Oct 2026
- 1.6.0 28 Aug 2026
- 1.5.0 07 Jan 2025
- 1.4.0 20 Dec 2024
- 1.3.0 28 May 2024
- 1.2.3 04 May 2023
- 1.2.2 28 Feb 2023
- 1.2.1 18 Aug 2022
- 1.2.0 07 Dec 2021
- 1.1.0 15 Sep 2021
- 1.0.0 02 Mar 2021
- 0.1.8 08 Feb 2021
- 0.1.7 08 Dec 2020
- 0.1.6 08 Dec 2020
- 0.1.5 08 Aug 2019
- 0.1.4 08 Jan 2019
- 0.1.3 20 Dec 2018
- 0.1.2+3 23 Oct 2018
- 0.1.2+2 24 Jul 2018
- 0.1.2+1 23 Jul 2018
- 0.1.2 20 Jun 2018
- 0.1.1 08 Jun 2018
- 0.1.0 04 Jun 2018
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 1.7.0 | 21 Oct 2026 | none | — | — | Details → |
| 1.6.0 | 28 Aug 2026 | none | — | — | Details → |
| 1.5.0 | 07 Jan 2025 | none | — | — | Details → |
| 1.4.0 | 20 Dec 2024 | none | — | — | Details → |
| 1.3.0 | 28 May 2024 | none | — | — | Details → |
| 1.2.3 | 04 May 2023 | none | — | — | Details → |
| 1.2.2 | 28 Feb 2023 | none | — | — | Details → |
| 1.2.1 | 18 Aug 2022 | none | — | — | Details → |
| 1.2.0 | 07 Dec 2021 | none | — | — | Details → |
| 1.1.0 | 15 Sep 2021 | none | — | — | Details → |
| 1.0.0 | 02 Mar 2021 | none | — | — | Details → |
| 0.1.8 | 08 Feb 2021 | none | — | — | Details → |
| 0.1.7 | 08 Dec 2020 | none | — | — | Details → |
| 0.1.6 | 08 Dec 2020 | none | — | — | Details → |
| 0.1.5 | 08 Aug 2019 | none | — | — | Details → |
| 0.1.4 | 08 Jan 2019 | none | — | — | Details → |
| 0.1.3 | 20 Dec 2018 | none | — | — | Details → |
| 0.1.2+3 | 23 Oct 2018 | none | — | — | Details → |
| 0.1.2+2 | 24 Jul 2018 | none | — | — | Details → |
| 0.1.2+1 | 23 Jul 2018 | none | — | — | Details → |
| 0.1.2 | 20 Jun 2018 | none | — | — | Details → |
| 0.1.1 | 08 Jun 2018 | none | — | — | Details → |
| 0.1.0 | 04 Jun 2018 | none | — | — | Details → |
All 23 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 pubspec_parse
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 pubspec_parse
Is pubspec_parse safe to use?
Vulert has no vulnerabilities on record for pubspec_parse in Pub 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 pubspec_parse's Vulert package health score?
Vulert scores pubspec_parse 100/100, which reads as healthy. 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 pubspec_parse affected?
No. 1.7.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.
How many vulnerabilities does pubspec_parse have?
0 vulnerabilities are recorded for pubspec_parse in the Pub 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 pubspec_parse vulnerabilities disclosed?
0 vulnerabilities were recorded for pubspec_parse 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 pubspec_parse 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 pubspec_parse for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pubspec_parse version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.