Vulnerability Database · Pub · Package report
freezed_annotation: vulnerability history, versions and safety
freezed_annotation 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 freezed_annotation 3.1.0 i
Updated on 23 Oct 2026
Good news: 3.1.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Maintaining
- Popularity Not enough data
- Community Not enough data
What to do: Stay on 3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 3.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 15 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 freezed_annotation, 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.
- 3.1.0 02 Jul 2025
- 3.0.0 25 Feb 2025
- 2.4.4 15 Jul 2024
- 2.4.3 09 Jul 2024
- 2.4.2 02 Jul 2024
- 2.4.1 12 Jul 2023
- 2.2.0 14 Oct 2022
- 2.1.0 15 Jul 2022
- 2.0.3 06 May 2022
- 2.0.1 20 Apr 2022
- 2.0.0 19 Apr 2022
- 1.1.0 11 Dec 2021
- 1.0.0 16 Nov 2021
- 0.15.0 08 Oct 2021
- 0.14.3 17 Jul 2021
- 0.14.2 13 May 2021
- 0.14.1 14 Mar 2021
- 0.14.0 04 Mar 2021
- 0.13.0-nullsafety.0 23 Jan 2021
- 0.12.0 19 Sep 2020
- 0.11.0+1 02 Aug 2020
- 0.11.0 13 Jun 2020
- 0.11.0-dev 01 Jun 2020
- 0.7.1 24 Feb 2020
- 0.7.0 21 Feb 2020
- 0.6.0 15 Feb 2020
- 0.4.0 13 Feb 2020
- 0.3.1 13 Feb 2020
- 0.3.0 13 Feb 2020
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 3.1.0 | 02 Jul 2025 | none | — | — | Details → |
| 3.0.0 | 25 Feb 2025 | none | — | — | Details → |
| 2.4.4 | 15 Jul 2024 | none | — | — | Details → |
| 2.4.3 | 09 Jul 2024 | none | — | — | Details → |
| 2.4.2 | 02 Jul 2024 | none | — | — | Details → |
| 2.4.1 | 12 Jul 2023 | none | — | — | Details → |
| 2.2.0 | 14 Oct 2022 | none | — | — | Details → |
| 2.1.0 | 15 Jul 2022 | none | — | — | Details → |
| 2.0.3 | 06 May 2022 | none | — | — | Details → |
| 2.0.1 | 20 Apr 2022 | none | — | — | Details → |
| 2.0.0 | 19 Apr 2022 | none | — | — | Details → |
| 1.1.0 | 11 Dec 2021 | none | — | — | Details → |
| 1.0.0 | 16 Nov 2021 | none | — | — | Details → |
| 0.15.0 | 08 Oct 2021 | none | — | — | Details → |
| 0.14.3 | 17 Jul 2021 | none | — | — | Details → |
| 0.14.2 | 13 May 2021 | none | — | — | Details → |
| 0.14.1 | 14 Mar 2021 | none | — | — | Details → |
| 0.14.0 | 04 Mar 2021 | none | — | — | Details → |
| 0.13.0-nullsafety.0 | 23 Jan 2021 | none | — | — | Details → |
| 0.12.0 | 19 Sep 2020 | none | — | — | Details → |
| 0.11.0+1 | 02 Aug 2020 | none | — | — | Details → |
| 0.11.0 | 13 Jun 2020 | none | — | — | Details → |
| 0.11.0-dev | 01 Jun 2020 | none | — | — | Details → |
| 0.7.1 | 24 Feb 2020 | none | — | — | Details → |
| 0.7.0 | 21 Feb 2020 | none | — | — | Details → |
| 0.6.0 | 15 Feb 2020 | none | — | — | Details → |
| 0.4.0 | 13 Feb 2020 | none | — | — | Details → |
| 0.3.1 | 13 Feb 2020 | none | — | — | Details → |
| 0.3.0 | 13 Feb 2020 | none | — | — | Details → |
All 29 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 freezed_annotation
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 freezed_annotation
Is freezed_annotation safe to use?
Vulert has no vulnerabilities on record for freezed_annotation 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 freezed_annotation's Vulert package health score?
Vulert scores freezed_annotation 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 freezed_annotation affected?
No. 3.1.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 freezed_annotation have?
0 vulnerabilities are recorded for freezed_annotation 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 freezed_annotation vulnerabilities disclosed?
0 vulnerabilities were recorded for freezed_annotation 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 freezed_annotation 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 freezed_annotation for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the freezed_annotation version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.