Vulnerability Database · npm · Package report

fs2: vulnerability history, versions and safety

Q: How do I monitor fs2 for upcoming vulnerabilities?

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

fs2 is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fs2 vulnerabilities

Vulert verdict on fs2 0.3.16 i

Updated on 23 Oct 2026

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

Package health score 62/100

Security Minor issues
Maintenance Maintaining
Popularity Niche
Community Inactive

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

Current release 0.3.16 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 408 packages i
Stars 19 i
OpenSSF scorecard 2/10 i
Last release 17 months ago i
Licence ISC i
Similar names fs 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for fs2, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.3.16	21 May 2025	none	ISC	—	Details →
0.3.15	02 Oct 2024	none	ISC	—	Details →
0.3.14	30 Sep 2024	none	ISC	—	Details →
0.3.13	30 Sep 2024	none	ISC	—	Details →
0.3.12	08 Sep 2024	none	ISC	—	Details →
0.3.11	08 Sep 2024	none	ISC	—	Details →
0.3.10	08 Sep 2024	none	ISC	—	Details →
0.4.0	08 Sep 2024	none	ISC	—	Details →
0.2.22	08 Dec 2023	none	ISC	—	Details →
0.3.9	19 Nov 2020	none	ISC	—	Details →
0.3.8	27 Apr 2020	none	ISC	—	Details →
0.3.7	07 Nov 2019	none	ISC	—	Details →
0.3.6	26 Sep 2019	none	ISC	—	Details →
0.3.5	10 Jul 2019	none	ISC	—	Details →
0.3.4	04 Feb 2019	none	ISC	—	Details →
0.3.3	04 Feb 2019	none	ISC	—	Details →
0.3.2	04 Feb 2019	none	ISC	—	Details →
0.3.1	31 Jan 2019	none	ISC	—	Details →
0.3.0	07 Jan 2019	none	ISC	—	Details →
0.2.21	15 Nov 2018	none	ISC	—	Details →
0.2.20	07 Nov 2018	none	ISC	—	Details →
0.2.19	31 Oct 2018	none	ISC	—	Details →
0.2.18	31 Oct 2018	none	ISC	—	Details →
0.2.17	31 Oct 2018	none	ISC	—	Details →
0.2.16	31 Oct 2018	none	ISC	—	Details →
0.2.15	25 Oct 2018	none	ISC	—	Details →
0.2.14	24 Oct 2018	none	ISC	—	Details →
0.2.13	24 Oct 2018	none	ISC	—	Details →
0.2.12	24 Oct 2018	none	ISC	—	Details →
0.2.11	23 Oct 2018	none	ISC	—	Details →
0.2.10	14 Sep 2018	none	ISC	—	Details →
0.2.9	13 Sep 2018	none	ISC	—	Details →
0.2.8	07 Sep 2018	none	ISC	—	Details →
0.2.7	05 Sep 2017	none	MIT	—	Details →
0.2.6	19 Jun 2017	none	MIT	—	Details →
0.2.5	16 Jun 2017	none	MIT	—	Details →
0.2.4	15 Mar 2017	none	MIT	—	Details →
0.2.3	14 Sep 2015	none	MIT	—	Details →
0.2.2	10 Sep 2015	none	MIT	—	Details →
0.2.1	27 Apr 2014	none	ISC	—	Details →
0.2.0	27 Apr 2014	none	ISC	—	Details →
0.1.5	10 Apr 2013	none	ISC	—	Details →
0.1.4	08 Feb 2013	none	ISC	—	Details →
0.1.3	08 Feb 2013	none	ISC	—	Details →
0.1.2	16 Jan 2013	none	ISC	—	Details →
0.1.1	04 Oct 2012	none	ISC	—	Details →
0.1.0	04 Oct 2012	none	ISC	—	Details →

All 47 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for fs2

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 fs2

Is fs2 safe to use?

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

Vulert scores fs2 62/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 fs2 affected?

No. 0.3.16, 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 fs2 should I use?

0.3.16 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 fs2 have?

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

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

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