Vulnerability Database · npm · Package report
@parcel/fs-write-stream-atomic: vulnerability history, versions and safety
@parcel/fs-write-stream-atomic is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @parcel/fs-write-stream-atomic 2.6.0 i
Updated on 23 Oct 2026
Good news: 2.6.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on 2.6.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.6.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 2.6.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 2 packages i
- Stars 44,006 i
- OpenSSF scorecard 2/10 i
- Last release 52 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 @parcel/fs-write-stream-atomic, 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.
- 2.6.1-nightly.2740 13 Jun 2022
- 2.6.1-nightly.2739 08 Jun 2022
- 2.6.1-nightly.2736 30 May 2022
- 2.6.1-nightly.2735 28 May 2022
- 2.6.1-nightly.2733 26 May 2022
- 2.6.0 25 May 2022
- 2.5.1-nightly.2728 25 May 2022
- 2.5.1-nightly.2726 24 May 2022
- 2.5.1-nightly.2722 23 May 2022
- 2.5.1-nightly.2721 22 May 2022
- 2.5.1-nightly.2720 21 May 2022
- 2.5.1-nightly.2719 18 May 2022
- 2.5.1-nightly.2715 14 May 2022
- 2.5.1-nightly.2714 13 May 2022
- 2.5.1-nightly.2713 11 May 2022
- 2.5.1-nightly.2712 10 May 2022
- 2.5.1-nightly.2711 09 May 2022
- 2.5.1-nightly.2709 08 May 2022
- 2.5.1-nightly.2708 07 May 2022
- 2.5.1-nightly.2705 05 May 2022
- 2.5.1-nightly.2703 04 May 2022
- 2.5.1-nightly.2700 02 May 2022
- 2.5.1-nightly.2698 01 May 2022
- 2.5.1-nightly.2697 30 Apr 2022
- 2.5.1-nightly.2696 27 Apr 2022
- 2.5.1-nightly.2693 23 Apr 2022
- 2.5.1-nightly.2692 22 Apr 2022
- 2.5.0 21 Apr 2022
- 2.4.2-nightly.2679 20 Apr 2022
- 2.4.2-nightly.2678 18 Apr 2022
- 2.4.2-nightly.2677 17 Apr 2022
- 2.4.2-nightly.2676 16 Apr 2022
- 2.4.2-nightly.2674 14 Apr 2022
- 2.4.2-nightly.2666 08 Apr 2022
- 2.4.2-nightly.2665 08 Apr 2022
- 2.4.2-nightly.2664 07 Apr 2022
- 2.4.2-nightly.2661 06 Apr 2022
- 2.4.2-nightly.2660 01 Apr 2022
- 2.4.1 31 Mar 2022
- 2.4.1-nightly.2657 31 Mar 2022
- 2.4.1-nightly.2656 30 Mar 2022
- 2.4.1-nightly.2655 29 Mar 2022
- 2.4.1-nightly.2654 24 Mar 2022
- 2.4.1-nightly.2653 23 Mar 2022
- 2.4.0 22 Mar 2022
- 2.3.3-nightly.2650 21 Mar 2022
- 2.3.3-nightly.2642 19 Mar 2022
- 2.3.3-nightly.2638 13 Mar 2022
- 2.3.3-nightly.2637 12 Mar 2022
- 2.3.3-nightly.2635 11 Mar 2022
- 2.3.3-nightly.2633 09 Mar 2022
- 2.3.3-nightly.2632 02 Mar 2022
- 2.3.3-nightly.2629 24 Feb 2022
- 2.3.3-nightly.2627 19 Feb 2022
- 2.3.2 18 Feb 2022
- 2.3.2-nightly.2625 11 Feb 2022
- 2.3.1 10 Feb 2022
- 2.3.0 09 Feb 2022
- 2.2.2-nightly.2616 04 Feb 2022
- 2.2.2-nightly.2615 01 Feb 2022
- 2.2.2-nightly.2614 31 Jan 2022
- 2.2.2-nightly.2609 18 Jan 2022
- 2.2.1 17 Jan 2022
- 2.2.1-nightly.2605 14 Jan 2022
- 2.2.0 12 Jan 2022
- 2.1.2-nightly.2601 11 Jan 2022
- 2.1.2-nightly.2600 08 Jan 2022
- 2.1.1 06 Jan 2022
- 2.1.1-nightly.2593 06 Jan 2022
- 2.1.0 05 Jan 2022
- 2.0.2-nightly.2589 05 Jan 2022
- 2.0.2-nightly.2585 03 Jan 2022
- 2.0.2-nightly.2584 02 Jan 2022
- 2.0.2-nightly.2581 30 Dec 2021
- 2.0.2-nightly.2576 26 Dec 2021
- 2.0.2-nightly.2575 20 Dec 2021
- 2.0.2-nightly.2573 17 Dec 2021
- 2.0.2-nightly.2572 17 Dec 2021
- 2.0.2-nightly.2571 16 Dec 2021
- 2.0.2-nightly.2569 14 Dec 2021
- 2.0.2-nightly.2566 12 Dec 2021
- 2.0.2-nightly.2564 12 Dec 2021
- 2.0.2-nightly.2563 09 Dec 2021
- 2.0.2-nightly.2558 01 Dec 2021
- 2.0.2-nightly.2556 30 Nov 2021
- 2.0.2-nightly.2554 29 Nov 2021
- 2.0.2-nightly.2549 25 Nov 2021
- 2.0.2-nightly.2548 24 Nov 2021
- 2.0.2-nightly.2541 22 Nov 2021
- 2.0.2-nightly.2540 17 Nov 2021
- 2.0.2-nightly.2536 15 Nov 2021
- 2.0.2-nightly.2534 13 Nov 2021
- 2.0.2-nightly.2533 09 Nov 2021
- 2.0.1 08 Nov 2021
- 2.0.1-nightly.2529 06 Nov 2021
- 2.0.1-nightly.2528 05 Nov 2021
- 2.0.1-nightly.2527 03 Nov 2021
- 2.0.1-nightly.2521 02 Nov 2021
- 2.0.1-nightly.2520 01 Nov 2021
- 2.0.1-nightly.2519 30 Oct 2021
- 2.0.1-nightly.2518 28 Oct 2021
- 2.0.1-nightly.2517 27 Oct 2021
- 2.0.1-nightly.2514 25 Oct 2021
- 2.0.1-nightly.2513 22 Oct 2021
- 2.0.1-nightly.2512 19 Oct 2021
- 2.0.1-nightly.2511 17 Oct 2021
- 2.0.1-nightly.2510 16 Oct 2021
- 2.0.1-nightly.2509 15 Oct 2021
- 2.0.1-nightly.2508 14 Oct 2021
- 2.0.0 13 Oct 2021
- 2.0.0-nightly.2506 12 Oct 2021
- 2.0.0-nightly.2503 12 Oct 2021
- 2.0.0-nightly.2501 11 Oct 2021
- 2.0.0-nightly.2500 10 Oct 2021
- 2.0.0-nightly.2497 09 Oct 2021
- 2.0.0-nightly.2491 08 Oct 2021
- 2.0.0-nightly.2488 07 Oct 2021
- 2.0.0-nightly.2483 06 Oct 2021
- 2.0.0-nightly.2479 05 Oct 2021
- 2.0.0-nightly.2476 04 Oct 2021
The newest 120 of 398 versions Vulert tracks. 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 @parcel/fs-write-stream-atomic
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
Questions
About @parcel/fs-write-stream-atomic
Is @parcel/fs-write-stream-atomic safe to use?
Vulert has no vulnerabilities on record for @parcel/fs-write-stream-atomic 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 @parcel/fs-write-stream-atomic's Vulert package health score?
Vulert scores @parcel/fs-write-stream-atomic 58/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 @parcel/fs-write-stream-atomic affected?
No. 2.6.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 @parcel/fs-write-stream-atomic should I use?
2.6.0 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 @parcel/fs-write-stream-atomic have?
0 vulnerabilities are recorded for @parcel/fs-write-stream-atomic 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 @parcel/fs-write-stream-atomic vulnerabilities disclosed?
0 vulnerabilities were recorded for @parcel/fs-write-stream-atomic 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 @parcel/fs-write-stream-atomic 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 @parcel/fs-write-stream-atomic for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @parcel/fs-write-stream-atomic version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.