---
title: "@npmcli/fs 6.0.0: release notes, upgrades and advisories"
description: "@npmcli/fs 6.0.0: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/@npmcli/fs
lang: en
---

[Packages](https://inlinr.com/packages)

# @npmcli/fs

6.0.0 · 15 May 2026 ISC 40.4M / week [Repository](https://github.com/npm/fs) [Homepage](https://github.com/npm/fs#readme) [npm](https://www.npmjs.com/package/@npmcli/fs) [Atom feed](https://inlinr.com/packages/feed/@npmcli/fs)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/@npmcli/fs/upgrade)

LineNewestSecurity

- 6.x 6.0.0 No known advisory Latest line
- 5.x 5.0.0 No known advisory [To 6.0.0](https://inlinr.com/packages/@npmcli/fs/upgrade/5.0.0-6.0.0)
- 4.x 4.0.0 No known advisory [To 6.0.0](https://inlinr.com/packages/@npmcli/fs/upgrade/4.0.0-6.0.0)
- 3.x 3.1.1 No known advisory [To 6.0.0](https://inlinr.com/packages/@npmcli/fs/upgrade/3.1.1-6.0.0)
- 2.x 2.1.2 No known advisory [To 6.0.0](https://inlinr.com/packages/@npmcli/fs/upgrade/2.1.2-6.0.0)
- 1.x 1.1.1 No known advisory [To 6.0.0](https://inlinr.com/packages/@npmcli/fs/upgrade/1.1.1-6.0.0)

## Latest releases

1. 6.x · latest line
2. ### [6.0.0](https://inlinr.com/packages/@npmcli/fs/releases/6.0.0 "Open this release") [](https://github.com/npm/fs/releases/tag/v6.0.0 "Read this release where it was published")  
15 May 2026

  - Breaking  
  [@npmcli/fs](https://inlinr.com/packages/@npmcli/fs) now supports node `^22.22.2 || ^24.15.0 || >=26.0.0`
  - Breaking  
  template-oss-apply
  - Bump to new node engine range
3. 5.x · maintenance
4. ### [5.0.0](https://inlinr.com/packages/@npmcli/fs/releases/5.0.0 "Open this release") [](https://github.com/npm/fs/releases/tag/v5.0.0 "Read this release where it was published")  
23 Oct 2025

  - Breaking  
  [@npmcli/fs](https://inlinr.com/packages/@npmcli/fs) now supports node `^20.17.0 || >=22.9.0`
  - Align to npm 11 node engine range
5. 4.x · maintenance
6. ### [4.0.0](https://inlinr.com/packages/@npmcli/fs/releases/4.0.0 "Open this release") [](https://github.com/npm/fs/releases/tag/v4.0.0 "Read this release where it was published")  
23 Sep 2024

  - Breaking  
  [@npmcli/fs](https://inlinr.com/packages/@npmcli/fs) now supports node `^18.17.0 || >=20.5.0`
  - Align to npm 10 node engine range

Dependency tracking

## Know when your own dependencies move

@npmcli/fs shipped a new major in the last 12 months, among 1 release. inlinr shows which of your projects are behind, and what the upgrade breaks.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/@npmcli/fs/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

## Same family

- [@npmcli/agent 25.6M/wk](https://inlinr.com/packages/@npmcli/agent)
- [@npmcli/arborist 9.7M/wk](https://inlinr.com/packages/@npmcli/arborist)
- [@npmcli/template-oss 8k/wk](https://inlinr.com/packages/@npmcli/template-oss)

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026\. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
