Vulnerability Database · npm · Package report

hfs: vulnerability history, versions and safety

hfs is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, from Jul 2024 to Aug 2025. 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 H1 L1
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 hfs 3.3.4 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.3.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Aug 2025 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Stars 3,958 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence GPL-3.0 i
  • Similar names fs, has 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 hfs, 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.4.0-rc5 20 Oct 2026 none GPL-3.0 — Details →
3.4.0-rc4 13 Oct 2026 none GPL-3.0 — Details →
3.4.0-beta3 05 Oct 2026 none GPL-3.0 — Details →
3.4.0-alpha2 01 Oct 2026 none GPL-3.0 — Details →
3.3.4 30 Sep 2026 none GPL-3.0 — Details →
3.4.0-alpha1 26 Sep 2026 none GPL-3.0 — Details →
3.3.3 24 Sep 2026 none GPL-3.0 — Details →
3.3.2 20 Sep 2026 none GPL-3.0 — Details →
3.3.1 17 Sep 2026 none GPL-3.0 — Details →
3.3.0 17 Sep 2026 none GPL-3.0 — Details →
3.3.0-rc8 13 Sep 2026 none GPL-3.0 — Details →
3.3.0-rc7 08 Sep 2026 none GPL-3.0 — Details →
3.3.0-rc6b 01 Sep 2026 none GPL-3.0 — Details →
3.3.0-rc5 29 Aug 2026 none GPL-3.0 — Details →
3.3.0-rc4 12 Aug 2026 none GPL-3.0 — Details →
3.3.0-beta3 07 Aug 2026 none GPL-3.0 — Details →
3.3.0-beta2 04 Aug 2026 none GPL-3.0 — Details →
3.3.0-alpha1 26 Jul 2026 none GPL-3.0 — Details →
3.2.2 24 Jul 2026 none GPL-3.0 — Details →
3.2.1 13 Jul 2026 none GPL-3.0 — Details →
3.2.0 05 Jul 2026 none GPL-3.0 — Details →
3.2.0-rc8 01 Jul 2026 none GPL-3.0 — Details →
3.2.0-rc7 17 Jun 2026 none GPL-3.0 — Details →
3.2.0-rc6 14 Jun 2026 none GPL-3.0 — Details →
3.2.0-rc5 07 Jun 2026 none GPL-3.0 — Details →
3.2.0-rc4 29 May 2026 none GPL-3.0 — Details →
3.1.7 28 May 2026 none GPL-3.0 — Details →
3.2.0-beta3 24 May 2026 none GPL-3.0 — Details →
3.2.0-beta2 15 May 2026 none GPL-3.0 — Details →
3.1.5 14 May 2026 none GPL-3.0 — Details →
3.2.0-alpha1.1 09 May 2026 none GPL-3.0 — Details →
3.1.4 05 May 2026 none GPL-3.0 — Details →
3.1.3 03 May 2026 none GPL-3.0 — Details →
3.1.2 01 May 2026 none GPL-3.0 — Details →
3.1.1 24 Apr 2026 none GPL-3.0 — Details →
3.1.0 18 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc12 12 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc11 11 Apr 2026 none GPL-3.0 — Details →
3.0.10 11 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc10 09 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc9 05 Apr 2026 none GPL-3.0 — Details →
3.0.9 05 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc8 02 Apr 2026 none GPL-3.0 — Details →
3.0.8 02 Apr 2026 none GPL-3.0 — Details →
3.1.0-rc7 30 Mar 2026 none GPL-3.0 — Details →
3.1.0-beta6 22 Mar 2026 none GPL-3.0 — Details →
3.1.0-beta5 17 Mar 2026 none GPL-3.0 — Details →
3.1.0-beta4 14 Mar 2026 none GPL-3.0 — Details →
3.1.0-alpha3.1 08 Mar 2026 none GPL-3.0 — Details →
3.1.0-alpha3 07 Mar 2026 none GPL-3.0 — Details →
3.1.0-alpha2 07 Mar 2026 none GPL-3.0 — Details →
3.1.0-alpha1 07 Mar 2026 none GPL-3.0 — Details →
3.0.7 04 Mar 2026 none GPL-3.0 — Details →
3.0.6 03 Mar 2026 none GPL-3.0 — Details →
3.0.5 28 Feb 2026 none GPL-3.0 — Details →
3.0.4 25 Feb 2026 none GPL-3.0 — Details →
3.0.3 14 Feb 2026 none GPL-3.0 — Details →
3.0.2 02 Feb 2026 none GPL-3.0 — Details →
3.0.2-beta0.1 29 Jan 2026 none GPL-3.0 — Details →
3.0.1 02 Jan 2026 none GPL-3.0 — Details →
3.0.0 20 Dec 2025 none GPL-3.0 — Details →
3.0.0-beta1 13 Dec 2025 none GPL-3.0 — Details →
0.57.27 06 Dec 2025 none GPL-3.0 — Details →
0.57.27-beta3 02 Dec 2025 none GPL-3.0 — Details →
0.57.27-beta2 30 Nov 2025 none GPL-3.0 — Details →
0.57.26 01 Nov 2025 none GPL-3.0 — Details →
0.57.24 24 Oct 2025 none GPL-3.0 — Details →
0.57.23 20 Oct 2025 none GPL-3.0 — Details →
0.57.22 17 Oct 2025 none GPL-3.0 — Details →
0.57.21 02 Oct 2025 none GPL-3.0 — Details →
0.57.20 27 Sep 2025 none GPL-3.0 — Details →
0.57.19 26 Sep 2025 none GPL-3.0 — Details →
0.57.18 17 Sep 2025 none GPL-3.0 — Details →
0.57.17 16 Sep 2025 none GPL-3.0 — Details →
0.57.16 13 Sep 2025 none GPL-3.0 — Details →
0.57.15 04 Sep 2025 none GPL-3.0 — Details →
0.57.14 29 Aug 2025 none GPL-3.0 — Details →
0.57.13 26 Aug 2025 none GPL-3.0 — Details →
0.57.12 19 Aug 2025 none GPL-3.0 — Details →
0.57.11 12 Aug 2025 none GPL-3.0 — Details →
0.57.10 12 Aug 2025 none GPL-3.0 — Details →
0.57.10-beta1 08 Aug 2025 L1 GPL-3.0 Yes Details →
0.57.9 06 Aug 2025 L1 GPL-3.0 Yes Details →
0.57.9-exp2 15 Jul 2025 L1 GPL-3.0 Yes Details →
0.57.9-beta1 13 Jul 2025 L1 GPL-3.0 Yes Details →
0.57.8 06 Jul 2025 L1 GPL-3.0 Yes Details →
0.57.7 01 Jul 2025 L1 GPL-3.0 Yes Details →
0.57.7-beta1 21 Jun 2025 L1 GPL-3.0 Yes Details →
0.57.6 19 Jun 2025 L1 GPL-3.0 Yes Details →
0.57.5 10 Jun 2025 L1 GPL-3.0 Yes Details →
0.57.4 06 Jun 2025 L1 GPL-3.0 Yes Details →
0.57.3 31 May 2025 L1 GPL-3.0 Yes Details →
0.57.3-rc4 29 May 2025 L1 GPL-3.0 Yes Details →
0.57.3-rc3 25 May 2025 L1 GPL-3.0 Yes Details →
0.57.3-rc2 21 May 2025 L1 GPL-3.0 Yes Details →
0.57.1 30 Apr 2025 L1 GPL-3.0 Yes Details →
0.57.0 26 Apr 2025 L1 GPL-3.0 Yes Details →
0.57.0-rc10 21 Apr 2025 L1 GPL-3.0 Yes Details →
0.57.0-rc9 21 Apr 2025 L1 GPL-3.0 Yes Details →
0.57.0-rc7 18 Apr 2025 L1 GPL-3.0 Yes Details →
0.57.0-rc8 16 Apr 2025 L1 — Yes Details →
0.57.0-rc6 07 Apr 2025 L1 — Yes Details →
0.57.0-beta5 06 Apr 2025 L1 — Yes Details →
0.57.0-beta4 24 Mar 2025 L1 — Yes Details →
0.57.0-beta3 14 Mar 2025 L1 — Yes Details →
0.57.0-beta2 07 Mar 2025 L1 — Yes Details →
0.57.0-alpha1 01 Mar 2025 L1 — Yes Details →
0.56.0 26 Feb 2025 L1 — Yes Details →
0.56.0-rc11 23 Feb 2025 L1 — Yes Details →
0.56.0-rc10 20 Feb 2025 L1 — Yes Details →
0.56.0-rc9 15 Feb 2025 L1 — Yes Details →
0.56.0-rc8 09 Feb 2025 L1 — Yes Details →
0.56.0-rc7 07 Feb 2025 L1 — Yes Details →
0.56.0-beta6 02 Feb 2025 L1 — Yes Details →
0.56.0-beta5 01 Feb 2025 L1 — Yes Details →
0.56.0-beta4 24 Jan 2025 L1 — Yes Details →
0.56.0-alpha3 21 Jan 2025 L1 — Yes Details →
0.56.0-alpha2 17 Jan 2025 L1 — Yes Details →
0.55.4 15 Jan 2025 L1 — Yes Details →
0.56.0-alpha1 13 Jan 2025 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 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 hfs

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 hfs

Is hfs safe to use?

Vulert records 2 vulnerabilities for hfs in npm: 0 critical, 1 high, 0 medium and 1 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 hfs's Vulert package health score?

Vulert scores hfs 73/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 hfs affected?

No. 3.3.4, 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 hfs should I use?

3.3.4 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 hfs have?

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

How often are new hfs vulnerabilities disclosed?

0 vulnerabilities were recorded for hfs in the last 12 months, and the oldest entry in this database dates to 05 Jul 2024. 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 hfs 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 hfs for upcoming vulnerabilities?

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