VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

graceful-fs: vulnerability history, versions and safety

graceful-fs 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 graceful-fs vulnerabilities

Vulert verdict on graceful-fs 4.2.11 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 4.2.11 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 807,578 packages i
  • Stars 1,301 i
  • OpenSSF scorecard 3/10 i
  • Last release 43 months ago i
  • Licence ISC 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 graceful-fs, 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
4.2.11 16 Mar 2023 none ISC — Details →
4.2.10 04 Apr 2022 none ISC — Details →
4.2.9 05 Jan 2022 none ISC — Details →
4.2.8 05 Aug 2021 none ISC — Details →
4.2.7 05 Aug 2021 none ISC — Details →
4.2.6 09 Feb 2021 none ISC — Details →
4.2.5 05 Feb 2021 none ISC — Details →
4.2.4 28 Apr 2020 none ISC — Details →
4.2.3 23 Oct 2019 none ISC — Details →
4.2.2 14 Aug 2019 none ISC — Details →
3.0.12 13 Aug 2019 none ISC — Details →
4.2.1 04 Aug 2019 none ISC — Details →
4.2.0 26 Jun 2019 none ISC — Details →
4.1.15 04 Nov 2018 none ISC — Details →
4.1.14 02 Nov 2018 none ISC — Details →
4.1.13 02 Nov 2018 none ISC — Details →
4.1.12 02 Nov 2018 none ISC — Details →
4.1.11 22 Nov 2016 none ISC — Details →
4.1.10 02 Nov 2016 none ISC — Details →
4.1.9 28 Sep 2016 none ISC — Details →
4.1.8 26 Sep 2016 none ISC — Details →
4.1.7 26 Sep 2016 none ISC — Details →
3.0.11 30 Aug 2016 none ISC — Details →
3.0.10 23 Aug 2016 none ISC — Details →
4.1.6 19 Aug 2016 none ISC — Details →
3.0.9 13 Aug 2016 none ISC — Details →
4.1.5 26 Jul 2016 none ISC — Details →
4.1.4 05 May 2016 none ISC — Details →
4.1.3 02 Feb 2016 none ISC — Details →
4.1.2 27 Jun 2015 none ISC — Details →
4.1.1 27 Jun 2015 none ISC — Details →
4.1.0 27 Jun 2015 none ISC — Details →
3.0.8 01 Jun 2015 none ISC — Details →
3.0.7 19 May 2015 none ISC — Details →
3.0.6 11 Mar 2015 none non-standard — Details →
3.0.5 30 Nov 2014 none non-standard — Details →
3.0.4 14 Oct 2014 none non-standard — Details →
3.0.3 06 Oct 2014 none non-standard — Details →
3.0.2 10 Jun 2014 none non-standard — Details →
3.0.1 07 Jun 2014 none non-standard — Details →
3.0.0 02 Jun 2014 none non-standard — Details →
2.0.3 20 Mar 2014 none non-standard — Details →
2.0.2 17 Feb 2014 none non-standard — Details →
2.0.1 07 Sep 2013 none non-standard — Details →
2.0.0 11 Jul 2013 none non-standard — Details →
1.2.3 10 Jul 2013 none non-standard — Details →
1.2.2 12 Jun 2013 none non-standard — Details →
1.2.1 30 Apr 2013 none non-standard — Details →
1.2.0 06 Feb 2013 none non-standard — Details →
1.1.14 20 Sep 2012 none non-standard — Details →
1.1.13 18 Sep 2012 none non-standard — Details →
1.1.12 18 Sep 2012 none non-standard — Details →
1.1.11 18 Sep 2012 none non-standard — Details →
1.1.10 28 Jul 2012 none non-standard — Details →
1.1.9 11 Jul 2012 none ISC — Details →
1.1.8 22 Mar 2012 none ISC — Details →
1.1.7 21 Mar 2012 none ISC — Details →
1.1.6 20 Mar 2012 none ISC — Details →
1.1.5 23 Jan 2012 none ISC — Details →
1.1.4 19 Jan 2012 none ISC — Details →
1.1.3 19 Jan 2012 none ISC — Details →
1.1.2 03 Dec 2011 none ISC — Details →
1.1.1 28 Nov 2011 none ISC — Details →
1.1.0 23 Nov 2011 none ISC — Details →
1.0.2 18 Nov 2011 none ISC — Details →
1.0.1 25 Sep 2011 none ISC — Details →
1.0.0 20 Jul 2011 none ISC — Details →

All 67 versions Vulert tracks for this package. 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 graceful-fs

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 graceful-fs

Is graceful-fs safe to use?

Vulert has no vulnerabilities on record for graceful-fs 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 graceful-fs's Vulert package health score?

Vulert scores graceful-fs 68/100, which reads as usable, but worth attention. 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 graceful-fs affected?

No. 4.2.11, 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 graceful-fs should I use?

4.2.11 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 graceful-fs have?

0 vulnerabilities are recorded for graceful-fs 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 graceful-fs vulnerabilities disclosed?

0 vulnerabilities were recorded for graceful-fs 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 graceful-fs 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 graceful-fs for upcoming vulnerabilities?

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