Vulnerability Database · Pub · Package report

table_calendar: vulnerability history, versions and safety

Q: How do I monitor table_calendar for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the Pub ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all table_calendar vulnerabilities

Vulert verdict on table_calendar 3.3.0 i

Updated on 23 Oct 2026

Good news: 3.3.0, 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 3.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

Current release 3.3.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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for table_calendar, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
3.3.0	01 Oct 2026	none	—	—	Details →
3.2.1	09 Aug 2026	none	—	—	Details →
3.2.0	08 Jan 2025	none	—	—	Details →
3.1.3	12 Dec 2024	none	—	—	Details →
3.1.2	09 Jun 2024	none	—	—	Details →
3.1.1	24 Mar 2024	none	—	—	Details →
3.1.0	09 Feb 2024	none	—	—	Details →
3.0.9	06 Jan 2023	none	—	—	Details →
3.0.8	30 Oct 2022	none	—	—	Details →
3.0.7	06 Sep 2022	none	—	—	Details →
3.0.6	29 May 2022	none	—	—	Details →
3.0.5	22 Mar 2022	none	—	—	Details →
3.0.4	20 Feb 2022	none	—	—	Details →
3.0.3	21 Oct 2021	none	—	—	Details →
3.0.2	10 Aug 2021	none	—	—	Details →
3.0.1	28 Jun 2021	none	—	—	Details →
3.0.0	06 Apr 2021	none	—	—	Details →
3.0.0-nullsafety.1	07 Mar 2021	none	—	—	Details →
3.0.0-nullsafety.0	22 Feb 2021	none	—	—	Details →
2.3.3	17 Dec 2020	none	—	—	Details →
2.3.2	10 Dec 2020	none	—	—	Details →
2.3.1	22 Nov 2020	none	—	—	Details →
2.3.0	15 Oct 2020	none	—	—	Details →
2.2.3	14 Mar 2020	none	—	—	Details →
2.2.2	04 Jan 2020	none	—	—	Details →
2.2.1	12 Nov 2019	none	—	—	Details →
2.2.0	06 Nov 2019	none	—	—	Details →
2.1.0	16 Oct 2019	none	—	—	Details →
2.0.2	21 Sep 2019	none	—	—	Details →
2.0.1	19 Aug 2019	none	—	—	Details →
2.0.0	29 Jul 2019	none	—	—	Details →
1.2.5	18 Jul 2019	none	—	—	Details →
1.2.4	11 Jul 2019	none	—	—	Details →
1.2.3	19 Jun 2019	none	—	—	Details →
1.2.2	24 May 2019	none	—	—	Details →
1.2.1	18 May 2019	none	—	—	Details →
1.2.0	27 Apr 2019	none	—	—	Details →
1.1.4	04 Apr 2019	none	—	—	Details →
1.1.3	03 Apr 2019	none	—	—	Details →
1.1.2	02 Apr 2019	none	—	—	Details →
1.1.1	30 Mar 2019	none	—	—	Details →
1.1.0	26 Mar 2019	none	—	—	Details →
1.0.2	22 Mar 2019	none	—	—	Details →
1.0.1	21 Mar 2019	none	—	—	Details →
1.0.0	21 Mar 2019	none	—	—	Details →
0.3.2	16 Mar 2019	none	—	—	Details →
0.3.1	15 Mar 2019	none	—	—	Details →
0.3.0	14 Mar 2019	none	—	—	Details →
0.2.2	12 Mar 2019	none	—	—	Details →
0.2.1	09 Mar 2019	none	—	—	Details →
0.2.0	06 Mar 2019	none	—	—	Details →
0.1.4	04 Mar 2019	none	—	—	Details →
0.1.3	27 Feb 2019	none	—	—	Details →
0.1.2	25 Feb 2019	none	—	—	Details →
0.1.1	23 Feb 2019	none	—	—	Details →
0.1.0	23 Feb 2019	none	—	—	Details →
0.0.2	22 Feb 2019	none	—	—	Details →
0.0.1	22 Feb 2019	none	—	—	Details →

All 58 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 table_calendar

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 table_calendar

Is table_calendar safe to use?

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

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

No. 3.3.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 table_calendar have?

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

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

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