Vulnerability Database · Pub · Package report

go_router: vulnerability history, versions and safety

go_router 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.

Vulert verdict on go_router 18.1.1 i

Updated on 23 Oct 2026

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

  • Current release 18.1.1 — 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 go_router, 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
18.1.1 20 Oct 2026 none — — Details →
18.1.0 14 Oct 2026 none — — Details →
18.0.2 28 Sep 2026 none — — Details →
18.0.1 02 Sep 2026 none — — Details →
18.0.0 24 Aug 2026 none — — Details →
17.5.0 10 Aug 2026 none — — Details →
17.4.0 04 Aug 2026 none — — Details →
17.3.0 02 Jun 2026 none — — Details →
17.2.3 01 May 2026 none — — Details →
17.2.2 20 Apr 2026 none — — Details →
17.2.1 13 Apr 2026 none — — Details →
17.2.0 02 Apr 2026 none — — Details →
17.1.0 03 Feb 2026 none — — Details →
17.0.1 10 Dec 2025 none — — Details →
17.0.0 06 Nov 2025 none — — Details →
16.3.0 22 Oct 2025 none — — Details →
16.2.5 15 Oct 2025 none — — Details →
16.2.4 23 Sep 2025 none — — Details →
16.2.3 23 Sep 2025 none — — Details →
16.2.2 20 Sep 2025 none — — Details →
16.2.1 29 Aug 2025 none — — Details →
16.2.0 18 Aug 2025 none — — Details →
16.1.0 04 Aug 2025 none — — Details →
16.0.0 01 Jul 2025 none — — Details →
15.2.4 24 Jun 2025 none — — Details →
15.2.3 19 Jun 2025 none — — Details →
15.2.2 19 Jun 2025 none — — Details →
15.2.1 18 Jun 2025 none — — Details →
15.2.0 12 Jun 2025 none — — Details →
15.1.3 06 Jun 2025 none — — Details →
15.1.2 08 May 2025 none — — Details →
15.1.1 22 Apr 2025 none — — Details →
15.1.0 21 Apr 2025 none — — Details →
15.0.0 16 Apr 2025 none — — Details →
14.8.1 26 Feb 2025 none — — Details →
14.8.0 07 Feb 2025 none — — Details →
14.7.2 28 Jan 2025 none — — Details →
14.7.1 24 Jan 2025 none — — Details →
14.7.0 25 Jan 2025 none — — Details →
14.6.3 06 Jan 2025 none — — Details →
14.6.2 03 Dec 2024 none — — Details →
14.6.1 21 Nov 2024 none — — Details →
14.6.0 13 Nov 2024 none — — Details →
14.5.0 12 Nov 2024 none — — Details →
14.4.1 04 Nov 2024 none — — Details →
14.4.0 04 Nov 2024 none — — Details →
14.3.0 04 Oct 2024 none — — Details →
14.2.9 03 Oct 2024 none — — Details →
14.2.8 24 Sep 2024 none — — Details →
14.2.7 23 Aug 2024 none — — Details →
14.2.6 20 Aug 2024 none — — Details →
14.2.5 20 Aug 2024 none — — Details →
14.2.3 05 Aug 2024 none — — Details →
14.2.2 01 Aug 2024 none — — Details →
14.2.1 11 Jul 2024 none — — Details →
14.2.0 13 Jun 2024 none — — Details →
14.1.4 28 May 2024 none — — Details →
14.1.3 21 May 2024 none — — Details →
14.1.2 17 May 2024 none — — Details →
14.1.1 14 May 2024 none — — Details →
14.1.0 09 May 2024 none — — Details →
14.0.2 29 Apr 2024 none — — Details →
14.0.1 25 Apr 2024 none — — Details →
14.0.0 24 Apr 2024 none — — Details →
13.2.5 24 Apr 2024 none — — Details →
13.2.4 11 Apr 2024 none — — Details →
13.2.3 08 Apr 2024 none — — Details →
13.2.2 28 Mar 2024 none — — Details →
13.2.1 15 Mar 2024 none — — Details →
13.2.0 09 Feb 2024 none — — Details →
13.1.0 28 Jan 2024 none — — Details →
13.0.1 04 Jan 2024 none — — Details →
13.0.0 21 Dec 2023 none — — Details →
12.1.3 07 Dec 2023 none — — Details →
12.1.1 09 Nov 2023 none — — Details →
12.1.0 03 Nov 2023 none — — Details →
12.0.3 03 Nov 2023 none — — Details →
12.0.2 03 Nov 2023 none — — Details →
12.0.1 27 Oct 2023 none — — Details →
12.0.0 18 Oct 2023 none — — Details →
11.1.4 12 Oct 2023 none — — Details →
11.1.3 09 Oct 2023 none — — Details →
11.1.2 28 Sep 2023 none — — Details →
11.1.1 26 Sep 2023 none — — Details →
11.1.0 26 Sep 2023 none — — Details →
11.0.1 26 Sep 2023 none — — Details →
11.0.0 21 Sep 2023 none — — Details →
10.2.0 18 Sep 2023 none — — Details →
10.1.4 18 Sep 2023 none — — Details →
10.1.3 18 Sep 2023 none — — Details →
10.1.2 29 Aug 2023 none — — Details →
10.1.1 28 Aug 2023 none — — Details →
10.1.0 17 Aug 2023 none — — Details →
10.0.0 21 Jul 2023 none — — Details →
9.1.1 20 Jul 2023 none — — Details →
9.1.0 19 Jul 2023 none — — Details →
9.0.3 07 Jul 2023 none — — Details →
9.0.2 06 Jul 2023 none — — Details →
9.0.1 06 Jul 2023 none — — Details →
9.0.0 26 Jun 2023 none — — Details →
8.2.0 23 Jun 2023 none — — Details →
8.1.0 22 Jun 2023 none — — Details →
8.0.5 15 Jun 2023 none — — Details →
8.0.4 15 Jun 2023 none — — Details →
8.0.3 13 Jun 2023 none — — Details →
8.0.2 12 Jun 2023 none — — Details →
8.0.1 08 Jun 2023 none — — Details →
8.0.0 07 Jun 2023 none — — Details →
7.1.1 22 May 2023 none — — Details →
7.1.0 22 May 2023 none — — Details →
7.0.2 19 May 2023 none — — Details →
7.0.1 11 May 2023 none — — Details →
7.0.0 29 Apr 2023 none — — Details →
6.5.9 28 Apr 2023 none — — Details →
6.5.8 24 Apr 2023 none — — Details →
6.5.7 17 Apr 2023 none — — Details →
6.5.6 12 Apr 2023 none — — Details →
6.5.5 05 Apr 2023 none — — Details →
6.5.4 05 Apr 2023 none — — Details →
6.5.3 03 Apr 2023 none — — Details →

The newest 120 of 256 versions Vulert tracks. 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 go_router

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 go_router

Is go_router safe to use?

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

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

No. 18.1.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 go_router have?

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

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

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