VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

victory-area: vulnerability history, versions and safety

victory-area is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm 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 victory-area vulnerabilities

Vulert verdict on victory-area 37.3.6 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 37.3.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 59 packages i
  • Stars 11,240 i
  • OpenSSF scorecard 3/10 i
  • Last release 21 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 victory-area, 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
37.3.6 14 Jan 2025 none MIT — Details →
37.3.5 19 Dec 2024 none MIT — Details →
37.3.4 09 Dec 2024 none MIT — Details →
37.3.3 06 Dec 2024 none MIT — Details →
37.3.2 12 Nov 2024 none MIT — Details →
37.3.1 01 Nov 2024 none MIT — Details →
37.3.0 24 Oct 2024 none MIT — Details →
37.2.0 15 Oct 2024 none MIT — Details →
37.1.2 08 Oct 2024 none MIT — Details →
37.1.1 05 Sep 2024 none MIT — Details →
37.1.0 29 Aug 2024 none MIT — Details →
37.0.3-next.0 16 May 2024 none MIT — Details →
37.0.2 04 Apr 2024 none MIT — Details →
37.0.1 25 Mar 2024 none MIT — Details →
37.0.1-next.2 22 Mar 2024 none MIT — Details →
37.0.1-next.1 22 Mar 2024 none MIT — Details →
37.0.1-next.0 22 Mar 2024 none MIT — Details →
37.0.0 18 Mar 2024 none MIT — Details →
36.9.2 13 Mar 2024 none MIT — Details →
36.9.2-next.3 20 Feb 2024 none MIT — Details →
36.9.2-next.1 16 Feb 2024 none MIT — Details →
36.9.2-next.0 13 Feb 2024 none MIT — Details →
36.9.1 06 Feb 2024 none MIT — Details →
36.9.1-next.0 06 Feb 2024 none MIT — Details →
36.9.0 05 Feb 2024 none MIT — Details →
36.8.6 01 Feb 2024 none MIT — Details →
36.8.5 31 Jan 2024 none MIT — Details →
36.8.5-next.0 31 Jan 2024 none MIT — Details →
36.8.4 29 Jan 2024 none MIT — Details →
36.8.3 29 Jan 2024 none MIT — Details →
36.8.2 16 Jan 2024 none MIT — Details →
36.8.1 09 Jan 2024 none MIT — Details →
36.7.0 28 Nov 2023 none MIT — Details →
36.6.12 02 Nov 2023 none MIT — Details →
36.6.11 13 Jun 2023 none MIT — Details →
36.6.10 01 May 2023 none MIT — Details →
36.6.8 26 Sep 2022 none MIT — Details →
36.6.7 14 Sep 2022 none MIT — Details →
36.6.6 31 Aug 2022 none MIT — Details →
36.6.5 23 Aug 2022 none MIT — Details →
36.6.4 19 Aug 2022 none MIT — Details →
36.6.3 19 Aug 2022 none MIT — Details →
36.6.2 17 Aug 2022 none MIT — Details →
36.6.1 16 Aug 2022 none MIT — Details →
36.6.0 04 Aug 2022 none MIT — Details →
36.5.3 27 Jun 2022 none MIT — Details →
36.5.2 23 Jun 2022 none MIT — Details →
36.5.1 23 Jun 2022 none MIT — Details →
36.5.0 07 Jun 2022 none MIT — Details →
36.4.1 25 May 2022 none MIT — Details →
36.4.0 10 May 2022 none MIT — Details →
36.3.2 14 Apr 2022 none MIT — Details →
36.3.0 14 Feb 2022 none MIT — Details →
36.2.2 14 Feb 2022 none MIT — Details →
36.2.1 28 Jan 2022 none MIT — Details →
36.2.0 03 Nov 2021 none MIT — Details →
36.1.0 26 Oct 2021 none MIT — Details →
36.0.0 07 Sep 2021 none MIT — Details →
35.11.4 02 Sep 2021 none MIT — Details →
35.11.3 31 Aug 2021 none MIT — Details →
35.11.2 30 Aug 2021 none MIT — Details →
35.11.0 23 Aug 2021 none MIT — Details →
35.10.1 13 Aug 2021 none MIT — Details →
35.10.0 04 Aug 2021 none MIT — Details →
35.9.3 23 Jul 2021 none MIT — Details →
35.9.2 22 Jul 2021 none MIT — Details →
35.9.0 24 Jun 2021 none MIT — Details →
35.8.2 26 May 2021 none MIT — Details →
35.8.1 24 May 2021 none MIT — Details →
35.8.0 19 May 2021 none MIT — Details →
35.7.2 18 May 2021 none MIT — Details →
35.7.1 14 May 2021 none MIT — Details →
35.6.4 12 May 2021 none MIT — Details →
35.6.2 07 May 2021 none MIT — Details →
35.6.1 05 May 2021 none MIT — Details →
35.6.0 04 May 2021 none MIT — Details →
35.5.1 12 Apr 2021 none MIT — Details →
35.4.11 04 Mar 2021 none MIT — Details →
35.4.10 02 Mar 2021 none MIT — Details →
35.4.8 01 Feb 2021 none MIT — Details →
35.4.7 27 Jan 2021 none MIT — Details →
35.4.6 05 Jan 2021 none MIT — Details →
35.4.5 05 Jan 2021 none MIT — Details →
35.4.4 25 Dec 2020 none MIT — Details →
35.4.3 07 Dec 2020 none MIT — Details →
35.4.1 01 Dec 2020 none MIT — Details →
35.4.0 25 Nov 2020 none MIT — Details →
35.3.5 09 Nov 2020 none MIT — Details →
35.3.4 07 Nov 2020 none MIT — Details →
35.3.3 02 Nov 2020 none MIT — Details →
35.3.2 29 Oct 2020 none MIT — Details →
35.3.1 20 Oct 2020 none MIT — Details →
35.3.0 14 Oct 2020 none MIT — Details →
35.2.0 08 Oct 2020 none MIT — Details →
35.1.1 28 Sep 2020 none MIT — Details →
35.1.0 25 Sep 2020 none MIT — Details →
35.0.8 30 Jul 2020 none MIT — Details →
35.0.7 29 Jul 2020 none MIT — Details →
35.0.5 17 Jul 2020 none MIT — Details →
35.0.4 16 Jul 2020 none MIT — Details →
35.0.3 08 Jul 2020 none — — Details →
35.0.2 01 Jul 2020 none — — Details →
35.0.0 27 Jun 2020 none — — Details →
34.3.12 22 Jun 2020 none — — Details →
34.3.8 26 May 2020 none — — Details →
34.3.7 22 May 2020 none — — Details →
34.3.6 18 May 2020 none — — Details →
34.3.5 15 May 2020 none — — Details →
34.3.0 12 May 2020 none — — Details →
34.2.2 11 May 2020 none — — Details →
34.2.1 09 May 2020 none — — Details →
34.2.0 06 May 2020 none — — Details →
34.1.3 09 Mar 2020 none — — Details →
34.1.1 06 Feb 2020 none — — Details →
34.1.0 04 Feb 2020 none — — Details →
34.0.0 21 Dec 2019 none — — Details →
33.1.7 06 Dec 2019 none — — Details →
33.1.6 01 Dec 2019 none — — Details →
33.1.2 01 Nov 2019 none — — Details →
33.1.0 25 Sep 2019 none — — Details →

The newest 120 of 154 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 victory-area

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 victory-area

Is victory-area safe to use?

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

Vulert scores victory-area 74/100, which reads as in good shape. 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 victory-area affected?

No. 37.3.6, 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.

Which version of victory-area should I use?

37.3.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does victory-area have?

0 vulnerabilities are recorded for victory-area in the npm 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 victory-area vulnerabilities disclosed?

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

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