VulertSecurity VulertSecurity

Vulnerability Database · Pub · Package report

personnummer: vulnerability history, versions and safety

personnummer is a package in the Pub ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Sep 2022 to Jan 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L2
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 personnummer vulnerabilities

Vulert verdict on personnummer 3.1.0 i

Updated on 23 Oct 2026

Good news: 3.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 86/100
  • 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 2 over 1 year · 0 in the last year i
  • Latest disclosure 11 Jan 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 43 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 personnummer, 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
3.1.0 12 Mar 2023 none — — Details →
3.0.5 11 Jan 2022 none — — Details →
3.0.4 04 Jun 2021 none — — Details →
3.0.3 17 Jun 2020 none — — Details →
3.0.2 17 Apr 2020 L2 — Yes Details →
3.0.1 17 Apr 2020 L2 — Yes Details →
3.0.0 04 Mar 2020 L2 — Yes Details →
2.1.0 13 Nov 2019 L2 — Yes Details →
2.0.0 27 Aug 2019 L2 — Yes Details →
1.0.2 01 Jun 2019 L2 — Yes Details →
1.0.1 01 Jun 2019 L2 — Yes Details →
1.0.0 01 Jun 2019 L2 — Yes Details →

All 12 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for personnummer

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-22963: personnummer/dart vulnerable to Improper Input Validation N/A low 3.0.3 19 Sep 2022
Duplicate of GHSA-4xh4-v2pq-jvhm in personnummer package N/A low 3.0.3 11 Jan 2023

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 personnummer

Is personnummer safe to use?

Vulert records 2 vulnerabilities for personnummer in Pub: 0 critical, 0 high, 0 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is personnummer's Vulert package health score?

Vulert scores personnummer 86/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 personnummer 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 personnummer have?

2 vulnerabilities are recorded for personnummer in the Pub ecosystem: 0 critical, 0 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new personnummer vulnerabilities disclosed?

0 vulnerabilities were recorded for personnummer in the last 12 months, and the oldest entry in this database dates to 19 Sep 2022. 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 personnummer 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 personnummer for upcoming vulnerabilities?

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