fs-utils — Greenflagged

fs extras and utilities to extend the node.js file system module. Used in Assemble and many other projects.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jonschlinkertdoowb

Keywords

filefile systemfsnodenode.jspathreadreadFilereadFileSyncutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years (published 2014); no provenance is expected and not a risk signal for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): doowb is a long-standing, highly-approved publisher in the Assemble ecosystem. This 2014 maintainer addition is a legitimate historical transition.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change jonschlinkert→doowb occurred in Jan 2014; both are well-known Assemble ecosystem maintainers. Legitimate historical transition, stable for this package.	ai	2026/04/24
phantom-deps	phantom-dep:delete	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:js-yaml	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:kind-of	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:relative	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:is-absolute	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:extend-shallow	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:normalize-path	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:matched	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
phantom-deps	phantom-dep:lazy-cache	AI (phantom-deps): lazy-cache is used for lazy-loading; static import analysis will always flag lazily-loaded deps as phantom. This is a stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:async	AI (phantom-deps): Dependency is loaded lazily via lazy-cache pattern; not a direct require but genuinely used at runtime. Stable false positive.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in fs-utils is a documented try/catch pattern for optionally loading a file as a Node module — a legitimate utility behavior, not a security risk.	ai	2026/04/24
dependencies	unvetted-dep:template	AI (dependencies): template is a jonschlinkert package from the same author/ecosystem; no supply-chain concern for this package.	ai	2026/04/24

Versions (showing 36 of 36)

Version	Deps	Published
0.7.0	17 / 2	2015-11-17
0.6.5	11 / 2	2015-11-04
0.6.4	11 / 2	2015-11-03
0.6.3	11 / 2	2015-10-31
0.6.2	10 / 2	2015-10-31
0.6.0	11 / 4	2014-10-24
0.5.0	9 / 4	2014-10-06
0.4.3	7 / 2	2014-05-09
0.4.2	7 / 2	2014-05-09
0.4.1	7 / 2	2014-04-25
0.4.0	7 / 2	2014-04-06
0.3.10	8 / 2	2014-04-05
0.3.9	8 / 2	2014-03-25
0.3.8	9 / 2	2014-03-21
0.3.7	9 / 2	2014-03-21
0.3.6	9 / 2	2014-02-09
0.3.5	9 / 2	2014-02-09
0.3.4	9 / 2	2014-02-08
0.3.3	9 / 2	2014-02-04
0.3.2	9 / 2	2014-02-04
0.3.1	9 / 2	2014-02-04
0.3.0	9 / 2	2014-02-03
0.2.3	8 / 2	2014-02-03
0.2.1	8 / 2	2014-02-01
0.2.0	8 / 2	2014-02-01
0.1.11	7 / 2	2014-01-24
0.1.10	7 / 2	2014-01-23
0.1.9	7 / 1	2014-01-18
0.1.8	7 / 1	2014-01-18
0.1.7	6 / 1	2014-01-18
0.1.6	7 / 2	2014-01-15
0.1.5	7 / 2	2014-01-14
0.1.4	4 / 4	2014-01-14
0.1.3	4 / 2	2014-01-13
0.1.1	4 / 2	2014-01-13
0.1.0	1 / 2	2014-01-13

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

INFO No provenance attestation provenance

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

v0.6.0

1 finding

INFO No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

INFO No provenance attestation provenance

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

v0.4.1

1 finding

INFO No provenance attestation provenance

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

v0.4.0

1 finding

INFO No provenance attestation provenance

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

v0.3.10

1 finding

INFO No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

INFO No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

INFO No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

INFO No provenance attestation provenance

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

v0.3.2

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2014-02-04) provenance

This version was published by a different npm account than previous versions on 2014-02-04. 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.

v0.3.1

1 finding

INFO No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

2 findings

HIGH Publisher changed: jonschlinkert → doowb (on 2014-02-03) provenance

This version was published by a different npm account than previous versions on 2014-02-03. 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.

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2014-02-01) provenance

This version was published by a different npm account than previous versions on 2014-02-01. 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.

v0.1.11

2 findings

HIGH Publisher changed: jonschlinkert → doowb (on 2014-01-24) provenance

This version was published by a different npm account than previous versions on 2014-01-24. 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.

v0.1.10

1 finding

INFO No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

INFO No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2014-01-14) provenance

This version was published by a different npm account than previous versions on 2014-01-14. 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.

v0.1.4

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: jonschlinkert → doowb (on 2014-01-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-01-14. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.3

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: doowb → jonschlinkert (on 2014-01-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-01-13. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.1

2 findings

HIGH Publisher changed: jonschlinkert → doowb (on 2014-01-13) provenance

This version was published by a different npm account than previous versions on 2014-01-13. 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.

v0.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.