VulertSecurity VulertSecurity

Vulnerability Database · Pub · Package report

provider: vulnerability history, versions and safety

provider is a package in the Pub ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Pub ecosystem.

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

Vulert verdict on provider 6.1.5+1 i

Updated on 23 Oct 2026

Good news: 6.1.5+1, the version you would install today, has no known vulnerabilities.

Package health score 87/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 6.1.5+1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 14 months ago 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 provider, 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
6.1.5+1 19 Aug 2025 none — — Details →
6.1.5 29 Apr 2025 none — — Details →
6.1.4 26 Mar 2025 none — — Details →
6.1.3 26 Mar 2025 none — — Details →
6.1.2 28 Feb 2024 none — — Details →
6.1.1 10 Nov 2023 none — — Details →
6.1.0 08 Nov 2023 none — — Details →
6.1.0-dev.1 24 Sep 2023 none — — Details →
6.1.0-dev.0 24 Sep 2023 none — — Details →
6.0.5 14 Dec 2022 none — — Details →
6.0.4 11 Oct 2022 none — — Details →
6.0.3 22 May 2022 none — — Details →
6.0.2 29 Dec 2021 none — — Details →
6.0.1 24 Sep 2021 none — — Details →
6.0.0 19 Aug 2021 none — — Details →
6.0.0-dev 12 Jul 2021 none — — Details →
5.0.0 04 Mar 2021 none — — Details →
5.0.0-nullsafety.5 20 Feb 2021 none — — Details →
5.0.0-nullsafety.4 17 Feb 2021 none — — Details →
5.0.0-nullsafety.3 18 Jan 2021 none — — Details →
5.0.0-nullsafety.2 18 Dec 2020 none — — Details →
5.0.0-nullsafety.1 10 Dec 2020 none — — Details →
5.0.0-dev.0 02 Mar 2021 none — — Details →
4.3.3 18 Jan 2021 none — — Details →
4.3.2+4 14 Jan 2021 none — — Details →
4.3.2+3 07 Dec 2020 none — — Details →
4.3.2+2 05 Sep 2020 none — — Details →
4.3.2+1 20 Aug 2020 none — — Details →
4.3.2 07 Aug 2020 none — — Details →
4.3.1 10 Jul 2020 none — — Details →
4.3.0 08 Jul 2020 none — — Details →
4.2.0 07 Jul 2020 none — — Details →
4.1.3+1 05 Jul 2020 none — — Details →
4.1.3 05 Jun 2020 none — — Details →
4.1.2 14 May 2020 none — — Details →
4.1.1 09 May 2020 none — — Details →
4.1.0 06 May 2020 none — — Details →
4.1.0-dev+3 11 Apr 2020 none — — Details →
4.1.0-dev+2 09 Mar 2020 none — — Details →
4.1.0-dev+1 06 Mar 2020 none — — Details →
4.1.0-dev 07 Feb 2020 none — — Details →
4.0.5+1 26 Apr 2020 none — — Details →
4.0.5 11 Apr 2020 none — — Details →
4.0.4 12 Feb 2020 none — — Details →
4.0.3 05 Feb 2020 none — — Details →
4.0.2 18 Jan 2020 none — — Details →
4.0.1 28 Dec 2019 none — — Details →
4.0.0 22 Dec 2019 none — — Details →
4.0.0-hotfix.1 25 Dec 2019 none — — Details →
4.0.0-dev 26 Nov 2019 none — — Details →
3.2.0 27 Nov 2019 none — — Details →
3.1.0+1 17 Oct 2019 none — — Details →
3.1.0 20 Aug 2019 none — — Details →
3.0.0+1 11 Jun 2019 none — — Details →
3.0.0 07 Jun 2019 none — — Details →
2.0.1+1 25 May 2019 none — — Details →
2.0.1 12 May 2019 none — — Details →
2.0.0+1 03 May 2019 none — — Details →
2.0.0 03 May 2019 none — — Details →
2.0.0-dev 10 Apr 2019 none — — Details →
1.6.1 21 Feb 2019 none — — Details →
1.6.0 20 Feb 2019 none — — Details →
1.5.0 11 Feb 2019 none — — Details →
1.4.0 04 Feb 2019 none — — Details →
1.3.0 29 Jan 2019 none — — Details →
1.2.0 25 Jan 2019 none — — Details →
1.1.1 22 Oct 2018 none — — Details →
1.1.0 21 Oct 2018 none — — Details →
1.0.0 19 Oct 2018 none — — Details →
0.0.1 19 Oct 2018 none — — Details →

All 70 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 provider

No vulnerability write-ups match this view

Search all 0 in the database →

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 provider

Is provider safe to use?

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

Vulert scores provider 87/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 provider affected?

No. 6.1.5+1, 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 provider have?

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

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

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