Vulnerability Database · npm · Package report

fstream-npm: vulnerability history, versions and safety

Q: How do I monitor fstream-npm for upcoming vulnerabilities?

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

fstream-npm 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 fstream-npm vulnerabilities

Vulert verdict on fstream-npm 1.2.1 i

Updated on 23 Oct 2026

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

Package health score 42/100

Security Minor issues
Maintenance Deprecated
Popularity Little adoption
Community Inactive

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

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

Current release 1.2.1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 81 packages i
Stars 30 i
OpenSSF scorecard 1/10 i
Last release 113 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for fstream-npm, 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
1.2.1	13 May 2017	none	ISC	—	Details →
1.2.0	07 Sep 2016	none	ISC	—	Details →
1.1.1	02 Aug 2016	none	ISC	—	Details →
1.1.0	17 May 2016	none	ISC	—	Details →
1.0.7	05 Nov 2015	none	ISC	—	Details →
1.0.6	05 Nov 2015	none	ISC	—	Details →
1.0.5	20 Aug 2015	none	ISC	—	Details →
1.0.4	08 Jul 2015	none	ISC	—	Details →
1.0.3	19 Jun 2015	none	ISC	—	Details →
1.0.2	20 Mar 2015	none	ISC	—	Details →
1.0.1	17 Oct 2014	none	ISC	—	Details →
1.0.0	31 Jul 2014	none	ISC	—	Details →
0.1.8	31 Jul 2014	none	ISC	—	Details →
0.1.7	19 May 2014	none	non-standard	—	Details →
0.1.6	11 Oct 2013	none	non-standard	—	Details →
0.1.5	29 May 2013	none	non-standard	—	Details →
0.1.4	10 Mar 2013	none	non-standard	—	Details →
0.1.3	22 Oct 2012	none	non-standard	—	Details →
0.1.2	10 Sep 2012	none	non-standard	—	Details →
0.1.1	13 Jul 2012	none	non-standard	—	Details →
0.1.0	04 Jun 2012	none	non-standard	—	Details →
0.0.6	04 Jun 2012	none	non-standard	—	Details →
0.0.5	17 Apr 2012	none	ISC	—	Details →
0.0.4	27 Mar 2012	none	ISC	—	Details →
0.0.3	27 Mar 2012	none	ISC	—	Details →
0.0.2	27 Mar 2012	none	ISC	—	Details →
0.0.1	27 Mar 2012	none	ISC	—	Details →

All 27 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 fstream-npm

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 fstream-npm

Is fstream-npm safe to use?

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

Vulert scores fstream-npm 42/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 fstream-npm affected?

No. 1.2.1, 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 fstream-npm should I use?

1.2.1 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 fstream-npm have?

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

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

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