@npmcli/fs ISC 14 versions

@npmcli/fs

npm Repository Homepage

filesystem utilities for the npm cli

14

Versions

ISC

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

saquibkhannpm-cli-opsreggiowlstronaut

Keywords

npmoss

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): nlf → lukekarrys is a routine npm CLI team maintainer rotation; both are long-standing GitHub/npm org members.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): isaacs removal is org-level maintainer cleanup within the @npmcli scope; not indicative of takeover.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2022 before Sigstore provenance was standard; @npmcli scope is trusted.	ai	2026/04/24
typosquat	typosquat.levenshtein:qs	AI (typosquat): False positive: @npmcli/fs is an official npm CLI scoped package by GitHub Inc. The Levenshtein match is against the bare name 'fs', not a typosquat of 'qs'.	ai	2026/04/21
typosquat	typosquat.levenshtein:pg	AI (typosquat): False positive: @npmcli/fs is an official npm CLI scoped package by GitHub Inc. No plausible impersonation of 'pg'.	ai	2026/04/21

Versions (showing 14 of 14)

Version	Deps	Published
6.0.0	1 / 3	2026-05-15
5.0.0	1 / 3	2025-10-23
4.0.0	1 / 3	2024-09-23
3.1.1	1 / 3	2024-05-07
3.1.0	1 / 3	2022-11-03
3.0.0	1 / 3	2022-10-12
2.1.2	2 / 3	2022-08-15
2.1.1	2 / 3	2022-07-20
2.1.0	2 / 3	2022-03-21
2.0.1	2 / 2	2022-02-23
2.0.0	2 / 2	2022-02-23
1.1.1	2 / 2	2022-02-10
1.1.0	2 / 2	2021-12-09
1.0.0	2 / 2	2021-08-25

v6.0.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.0.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.2

2 findings

HIGH Publisher changed: nlf → gar (on 2022-08-15) provenance

This version was published by a different npm account than previous versions on 2022-08-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

2 findings

HIGH Publisher changed: nlf → lukekarrys (on 2022-07-20) provenance

This version was published by a different npm account than previous versions on 2022-07-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

2 findings

HIGH Publisher changed: nlf → lukekarrys (on 2022-03-21) provenance

This version was published by a different npm account than previous versions on 2022-03-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

2 findings

HIGH Publisher changed: nlf → lukekarrys (on 2022-02-23) provenance

This version was published by a different npm account than previous versions on 2022-02-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings

HIGH Publisher changed: nlf → lukekarrys (on 2022-02-23) provenance

This version was published by a different npm account than previous versions on 2022-02-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.