VulertSecurity VulertSecurity

Vulnerability Database · Pub · Package report

built_collection: vulnerability history, versions and safety

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

Vulert verdict on built_collection 5.1.2 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.1.2 — 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 built_collection, 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
5.1.2 28 Sep 2026 none — — Details →
5.1.1 03 Sep 2021 none — — Details →
5.1.0 11 Jun 2021 none — — Details →
5.0.0 09 Feb 2021 none — — Details →
5.0.0-nullsafety.0 17 Nov 2020 none — — Details →
4.3.2 01 Jan 2020 none — — Details →
4.3.1 31 Dec 2019 none — — Details →
4.3.0 15 Nov 2019 none — — Details →
4.2.2 12 May 2019 none — — Details →
4.2.1 06 May 2019 none — — Details →
4.2.0 02 Apr 2019 none — — Details →
4.1.0 03 Dec 2018 none — — Details →
4.0.0 20 Aug 2018 none — — Details →
3.1.3 23 Jul 2018 none — — Details →
3.1.2 23 Jul 2018 none — — Details →
3.1.1 26 Mar 2018 none — — Details →
3.0.5 18 Feb 2018 none — — Details →
3.0.4 31 Jan 2018 none — — Details →
3.0.3 29 Jan 2018 none — — Details →
3.0.2 23 Jan 2018 none — — Details →
3.0.1 16 Jan 2018 none — — Details →
3.0.0 08 Jan 2018 none — — Details →
2.1.3 08 Jan 2018 none — — Details →
2.1.2 21 Dec 2017 none — — Details →
2.1.1 21 Dec 2017 none — — Details →
2.1.0 04 Dec 2017 none — — Details →
2.0.0 20 Nov 2017 none — — Details →
1.6.2 16 Nov 2017 none — — Details →
1.6.1 09 Nov 2017 none — — Details →
1.6.0 17 Oct 2017 none — — Details →
1.5.0 12 Jul 2017 none — — Details →
1.4.1 20 Jun 2017 none — — Details →
1.4.0 11 Apr 2017 none — — Details →
1.3.1 07 Apr 2017 none — — Details →
1.3.0 22 Dec 2016 none — — Details →
1.2.0 11 Nov 2016 none — — Details →
1.0.6 19 Oct 2016 none — — Details →
1.0.5 15 Sep 2016 none — — Details →
1.0.4 15 Jul 2016 none — — Details →
1.0.3 18 May 2016 none — — Details →
1.0.2 18 Mar 2016 none — — Details →
1.0.1 23 Feb 2016 none — — Details →
1.0.0 13 Aug 2015 none — — Details →
0.4.0 12 Jun 2015 none — — Details →
0.3.1 15 May 2015 none — — Details →
0.3.0 15 May 2015 none — — Details →
0.2.0 14 May 2015 none — — Details →
0.1.1 19 Apr 2015 none — — Details →
0.1.0 17 Apr 2015 none — — Details →
0.0.1 07 Apr 2015 none — — Details →

All 50 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 built_collection

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 built_collection

Is built_collection safe to use?

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

Vulert scores built_collection 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 built_collection affected?

No. 5.1.2, 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 built_collection have?

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

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

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