VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

fury-adapter-swagger: vulnerability history, versions and safety

fury-adapter-swagger is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 39 releases, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 fury-adapter-swagger vulnerabilities

Vulert verdict on fury-adapter-swagger 0.29.0 i

Updated on 23 Oct 2026

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

Package health score 43/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Inactive

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release 0.29.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 01 Sep 2020 i
  • Highest CVSS 7.3 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 79 i
  • OpenSSF scorecard 3/10 i
  • Last release 78 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 fury-adapter-swagger, 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
0.29.0 20 Apr 2020 none MIT — Details →
0.28.3 17 Mar 2020 none MIT — Details →
0.28.2 07 Feb 2020 none MIT — Details →
0.28.1 30 Jan 2020 none MIT — Details →
0.28.0 06 Dec 2019 none MIT — Details →
0.27.2 08 Aug 2019 none MIT — Details →
0.27.1 04 Jul 2019 none MIT — Details →
0.27.0 02 Jul 2019 none MIT — Details →
0.26.0 11 Jun 2019 none MIT — Details →
0.25.1 29 Apr 2019 none MIT — Details →
0.25.0 26 Mar 2019 none MIT — Details →
0.24.2 18 Mar 2019 none MIT — Details →
0.24.1 05 Mar 2019 none MIT — Details →
0.24.0 26 Feb 2019 none MIT — Details →
0.23.2 31 Jan 2019 none MIT — Details →
0.23.1 10 Jan 2019 none MIT — Details →
0.23.0 04 Jan 2019 none MIT — Details →
0.22.7 11 Dec 2018 none MIT — Details →
0.22.6 07 Dec 2018 none MIT — Details →
0.22.5 07 Dec 2018 none MIT — Details →
0.22.4 29 Nov 2018 none MIT — Details →
0.22.3 27 Nov 2018 none MIT — Details →
0.22.2 25 Oct 2018 none MIT — Details →
0.22.1 23 Oct 2018 none MIT — Details →
0.22.0 11 Oct 2018 none MIT — Details →
0.21.1 10 Sep 2018 none MIT — Details →
0.21.0 07 Sep 2018 none MIT — Details →
0.20.0 04 Sep 2018 none MIT — Details →
0.19.2 21 Aug 2018 none MIT — Details →
0.19.1 07 Jun 2018 none MIT — Details →
0.19.0 28 May 2018 none MIT — Details →
0.18.4 18 May 2018 none MIT — Details →
0.18.3 03 May 2018 none MIT — Details →
0.18.2 25 Apr 2018 none MIT — Details →
0.18.1 02 Apr 2018 none MIT — Details →
0.18.0 16 Mar 2018 none MIT — Details →
0.17.0 13 Feb 2018 none MIT — Details →
0.16.1 17 Jan 2018 none MIT — Details →
0.16.0 05 Dec 2017 none MIT — Details →
0.15.2 30 Nov 2017 none MIT — Details →
0.15.1 10 Nov 2017 none MIT — Details →
0.15.0 06 Nov 2017 none MIT — Details →
0.14.3 24 Oct 2017 none MIT — Details →
0.14.2 18 Oct 2017 none MIT — Details →
0.14.1 17 Oct 2017 none MIT — Details →
0.14.0 03 Oct 2017 none MIT — Details →
0.13.4 22 Sep 2017 none MIT — Details →
0.13.3 25 Aug 2017 none MIT — Details →
0.13.2 21 Aug 2017 none MIT — Details →
0.13.1 11 Aug 2017 none MIT — Details →
0.13.0 08 Aug 2017 none MIT — Details →
0.12.1 21 Jul 2017 none MIT — Details →
0.12.0 11 Jul 2017 none MIT — Details →
0.12.0-beta.3 04 Jul 2017 none MIT — Details →
0.12.0-beta.2 13 Jun 2017 none MIT — Details →
0.12.0-beta.1 08 Jun 2017 none MIT — Details →
0.11.1 25 Apr 2017 none MIT — Details →
0.11.0 11 Apr 2017 none MIT — Details →
0.10.0 31 Mar 2017 none MIT — Details →
0.9.13 09 Feb 2017 none MIT — Details →
0.9.12 13 Dec 2016 none MIT — Details →
0.9.11 25 Nov 2016 none MIT — Details →
0.9.10 24 Nov 2016 none MIT — Details →
0.9.9 15 Nov 2016 none MIT — Details →
0.9.8 31 Oct 2016 none MIT — Details →
0.9.7 25 Oct 2016 none MIT — Details →
0.9.6 10 Oct 2016 H1 MIT Yes Details →
0.9.5 01 Sep 2016 H1 MIT Yes Details →
0.9.4 30 Aug 2016 H1 MIT Yes Details →
0.9.3 30 Aug 2016 H1 MIT Yes Details →
0.9.2 28 Aug 2016 H1 MIT Yes Details →
0.9.1 27 Jul 2016 H1 MIT Yes Details →
0.9.0 27 Jul 2016 H1 MIT Yes Details →
0.8.1 13 Jul 2016 H1 MIT Yes Details →
0.8.0 01 Jul 2016 H1 MIT Yes Details →
0.8.0-pre.19 30 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.18 30 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.16 17 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.15 09 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.14 08 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.12 07 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.10 05 Jun 2016 H1 MIT Yes Details →
0.8.0-pre.9 31 May 2016 H1 MIT Yes Details →
0.8.0-pre.8 31 May 2016 H1 MIT Yes Details →
0.8.0-pre.7 24 May 2016 H1 MIT Yes Details →
0.8.0-pre.4 17 May 2016 H1 MIT Yes Details →
0.8.0-pre.5 17 May 2016 H1 MIT Yes Details →
0.8.0-pre.2 16 May 2016 H1 MIT Yes Details →
0.8.0-pre.1 06 May 2016 H1 MIT Yes Details →
0.8.0-pre.0 29 Apr 2016 H1 MIT Yes Details →
0.7.3 12 Apr 2016 H1 MIT Yes Details →
0.7.2 18 Feb 2016 H1 MIT Yes Details →
0.7.1 15 Feb 2016 H1 MIT Yes Details →
0.7.0 04 Feb 2016 H1 MIT Yes Details →
0.6.2 13 Jan 2016 H1 MIT Yes Details →
0.6.1 11 Jan 2016 H1 MIT Yes Details →
0.6.0 14 Dec 2015 H1 MIT Yes Details →
0.5.2 10 Dec 2015 H1 MIT Yes Details →
0.5.1 10 Dec 2015 H1 MIT Yes Details →
0.5.0 08 Dec 2015 H1 MIT Yes Details →
0.4.0 02 Dec 2015 H1 — Yes Details →
0.3.2 30 Nov 2015 H1 — Yes Details →
0.3.1 25 Nov 2015 H1 — Yes Details →
0.3.0 19 Nov 2015 H1 — Yes Details →
0.2.0 17 Nov 2015 H1 — Yes Details →
0.1.0 25 Sep 2015 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for fury-adapter-swagger

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-1000249: Arbitrary File Read Vulnerability in fury-adapter-swagger 7.3 high 0.9.7 01 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 fury-adapter-swagger

Is fury-adapter-swagger safe to use?

Vulert records 1 vulnerabilities for fury-adapter-swagger in npm: 0 critical, 1 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 fury-adapter-swagger's Vulert package health score?

Vulert scores fury-adapter-swagger 43/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of fury-adapter-swagger affected?

No. 0.29.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.

Which version of fury-adapter-swagger should I use?

0.12.0-beta.3 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 fury-adapter-swagger have?

1 vulnerability is recorded for fury-adapter-swagger in the npm ecosystem: 0 critical, 1 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 fury-adapter-swagger vulnerabilities disclosed?

0 vulnerabilities were recorded for fury-adapter-swagger in the last 12 months, and the oldest entry in this database dates to 01 Sep 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 fury-adapter-swagger 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 fury-adapter-swagger for upcoming vulnerabilities?

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