VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@uppy/companion: vulnerability history, versions and safety

@uppy/companion is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 19 releases, from Aug 2020 to Mar 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H3
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 @uppy/companion vulnerabilities

Vulert verdict on @uppy/companion 7.2.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 7.2.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 04 Mar 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 31,027 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 @uppy/companion, 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
7.2.0 16 Oct 2026 none MIT — Details →
7.1.1 30 Sep 2026 none MIT — Details →
7.1.0 28 Sep 2026 none MIT — Details →
7.0.3 25 Sep 2026 none MIT — Details →
7.0.2 07 Sep 2026 none MIT — Details →
7.0.1 07 Sep 2026 none MIT — Details →
7.0.0 26 Aug 2026 none MIT — Details →
6.2.2 25 Mar 2026 none MIT — Details →
6.2.1 02 Dec 2025 none MIT — Details →
6.2.0 03 Nov 2025 none MIT — Details →
6.1.1 17 Oct 2025 none MIT — Details →
6.1.0 08 Oct 2025 none MIT — Details →
6.0.2 16 Sep 2025 none MIT — Details →
6.0.1 28 Aug 2025 none MIT — Details →
6.0.0 22 Aug 2025 none MIT — Details →
5.9.1 29 Jul 2025 none MIT — Details →
5.9.0 29 Jul 2025 none MIT — Details →
5.8.0 02 Jun 2025 none MIT — Details →
5.7.0 18 May 2025 none MIT — Details →
5.6.0 08 Apr 2025 none MIT — Details →
5.5.2 25 Feb 2025 none MIT — Details →
5.5.1 22 Jan 2025 none MIT — Details →
5.5.0 15 Jan 2025 none MIT — Details →
5.4.1 08 Jan 2025 none MIT — Details →
5.4.0 06 Jan 2025 none MIT — Details →
5.3.0 17 Dec 2024 none MIT — Details →
5.2.0 05 Dec 2024 none MIT — Details →
5.1.4 11 Nov 2024 none MIT — Details →
5.1.3 31 Oct 2024 none MIT — Details →
5.1.2 15 Oct 2024 none MIT — Details →
5.1.1 20 Sep 2024 none MIT — Details →
5.1.0 29 Aug 2024 none MIT — Details →
5.0.5 16 Aug 2024 none MIT — Details →
5.0.4 15 Jul 2024 none MIT — Details →
5.0.3 15 Jul 2024 none MIT — Details →
5.0.2 15 Jul 2024 none MIT — Details →
5.0.1 15 Jul 2024 none MIT — Details →
5.0.0 10 Jul 2024 none MIT — Details →
4.15.1 03 Jul 2024 none MIT — Details →
5.0.0-beta.12 02 Jul 2024 none MIT — Details →
4.15.0 02 Jul 2024 none MIT — Details →
5.0.0-beta.11 27 Jun 2024 none MIT — Details →
5.0.0-beta.10 19 Jun 2024 none MIT — Details →
4.14.0 18 Jun 2024 none MIT — Details →
5.0.0-beta.9 04 Jun 2024 none MIT — Details →
5.0.0-beta.8 23 May 2024 none MIT — Details →
5.0.0-beta.7 22 May 2024 none MIT — Details →
4.13.3 22 May 2024 none MIT — Details →
5.0.0-beta.6 14 May 2024 none MIT — Details →
5.0.0-beta.5 03 May 2024 none MIT — Details →
4.13.2 03 May 2024 none MIT — Details →
5.0.0-beta.4 29 Apr 2024 none MIT — Details →
5.0.0-beta.3 15 Apr 2024 none MIT — Details →
5.0.0-beta.2 11 Apr 2024 none MIT — Details →
4.13.1 10 Apr 2024 none MIT — Details →
5.0.0-beta.1 28 Mar 2024 none MIT — Details →
4.13.0 27 Mar 2024 none MIT — Details →
4.12.3 22 Feb 2024 none MIT — Details →
4.12.2 20 Feb 2024 none MIT — Details →
4.12.1 19 Feb 2024 none MIT — Details →
4.12.0 12 Dec 2023 none MIT — Details →
4.11.0 08 Nov 2023 none MIT — Details →
4.10.1 23 Oct 2023 none MIT — Details →
4.10.0 20 Oct 2023 none MIT — Details →
4.9.1 29 Sep 2023 none MIT — Details →
4.9.0 18 Sep 2023 none MIT — Details →
4.5.4 15 Sep 2023 none MIT — Details →
4.5.3 15 Sep 2023 none MIT — Details →
4.5.2 15 Sep 2023 none MIT — Details →
4.8.2 05 Sep 2023 none MIT — Details →
4.8.1 23 Aug 2023 none MIT — Details →
4.8.0 15 Aug 2023 none MIT — Details →
4.7.0 13 Jul 2023 none MIT — Details →
4.6.0 06 Jul 2023 none MIT — Details →
4.5.1 19 Jun 2023 none MIT — Details →
4.5.0 18 Apr 2023 none MIT — Details →
4.4.0 04 Apr 2023 none MIT — Details →
4.3.0 13 Feb 2023 none MIT — Details →
4.2.0 26 Jan 2023 none MIT — Details →
4.1.1 16 Nov 2022 none MIT — Details →
4.1.0 10 Nov 2022 none MIT — Details →
4.0.5 19 Oct 2022 none MIT — Details →
4.0.4 19 Oct 2022 none MIT — Details →
4.0.3 25 Sep 2022 none MIT — Details →
4.0.2 25 Sep 2022 none MIT — Details →
4.0.1 30 Aug 2022 none MIT — Details →
4.0.0 22 Aug 2022 none ISC — Details →
3.7.2 17 Aug 2022 none ISC — Details →
4.0.0-beta.4 16 Aug 2022 none ISC — Details →
4.0.0-beta.3 03 Aug 2022 none ISC — Details →
4.0.0-beta.2 27 Jul 2022 none ISC — Details →
3.7.1 27 Jul 2022 none ISC — Details →
4.0.0-beta.1 06 Jul 2022 none ISC — Details →
3.7.0 06 Jul 2022 none ISC — Details →
4.0.0-beta 30 May 2022 none ISC — Details →
3.6.0 30 May 2022 none ISC — Details →
3.5.2 27 Apr 2022 none ISC — Details →
3.5.1 27 Apr 2022 none ISC — Details →
3.5.0 24 Mar 2022 none ISC — Details →
3.4.0 16 Mar 2022 none ISC — Details →
3.3.1 02 Mar 2022 none — — Details →
3.3.0 17 Feb 2022 H1 — Yes Details →
3.2.1 16 Feb 2022 H1 — Yes Details →
3.2.0 14 Feb 2022 H1 — Yes Details →
3.1.5 04 Jan 2022 H1 — Yes Details →
3.1.4 21 Dec 2021 H1 — Yes Details →
3.1.3 09 Dec 2021 H1 — Yes Details →
3.1.2 07 Dec 2021 H1 — Yes Details →
2.12.3 15 Nov 2021 H1 — Yes Details →
3.1.1 14 Oct 2021 H1 — Yes Details →
3.1.0 06 Oct 2021 H1 — Yes Details →
3.0.1 26 Aug 2021 H1 — Yes Details →
3.0.0 24 Aug 2021 H1 — Yes Details →
2.12.2 13 Aug 2021 H1 — Yes Details →
2.13.0-alpha.0 02 Aug 2021 H1 — Yes Details →
2.12.1 02 Aug 2021 H1 — Yes Details →
2.12.0 29 Jul 2021 H1 — Yes Details →
2.11.1 13 Jul 2021 H1 — Yes Details →
2.11.0 30 Jun 2021 H1 — Yes Details →
2.10.1 28 May 2021 H1 — Yes Details →

The newest 120 of 186 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for @uppy/companion

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-8205: Server-Side Request Forgery in @uppy/companion 7.5 high 1.13.2 13 Aug 2020
CVE-2022-0528: Incorrect Authorization in @uppy/companion 7.5 high 3.3.1 04 Mar 2022
CVE-2020-8135: Server-Side Request Forgery in @uppy/companion N/A high 1.9.3 03 Sep 2020

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 @uppy/companion

Is @uppy/companion safe to use?

Vulert records 3 vulnerabilities for @uppy/companion in npm: 0 critical, 3 high, 0 medium and 0 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 @uppy/companion's Vulert package health score?

Vulert scores @uppy/companion 79/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 @uppy/companion affected?

No. 7.2.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 @uppy/companion have?

3 vulnerabilities are recorded for @uppy/companion in the npm ecosystem: 0 critical, 3 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 @uppy/companion vulnerabilities disclosed?

0 vulnerabilities were recorded for @uppy/companion in the last 12 months, and the oldest entry in this database dates to 13 Aug 2020. 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 @uppy/companion 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 @uppy/companion for upcoming vulnerabilities?

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