@flowfuse/driver-localfs No license 31 versions

@flowfuse/driver-localfs

npm Repository Homepage

31

Versions

—

License

No

Install Scripts

Missing

Provenance

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

hardillbknollearyflowfuse-user

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): flowfuse-user is the org's publishing account with 38 approved packages; transition from hardillb appears to be a legitimate org consolidation.	ai	2026/05/31
phantom-deps	phantom-dep:@flowfuse/nr-launcher	AI (phantom-deps): Same-org dependency used transitively or via dynamic require; stable false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@flowfuse/mqtt-schema-agent	AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires but usage may be indirect. Stable FP.	ai	2026/05/29
semgrep	semgrep:child-process-import	AI (semgrep): Driver legitimately spawns/kills Node-RED processes; child_process use is core to its function.	ai	2026/05/27
bogus-package	bogus-package	AI (bogus-package): FlowFuse org publishes many versioned driver packages by design; not spam.	ai	2026/05/27
semgrep	semgrep:child-process-spawn	AI (semgrep): Spawns Node.js runtime for managed Node-RED instances; expected behavior for a process driver.	ai	2026/05/27
semgrep	semgrep:child-process-exec	AI (semgrep): taskkill exec is Windows-only process termination for managed PIDs; legitimate driver behavior.	ai	2026/05/27

Versions (showing 31 of 31)

Version	Deps	Published
2.31.0	6 / 5	2026-06-04
2.30.1	6 / 5	2026-05-08
2.30.0	6 / 5	2026-05-07
2.29.1	6 / 5	2026-04-09
2.29.0	6 / 5	2026-04-09
2.28.1	6 / 5	2026-03-25
2.28.0	6 / 5	2026-03-12
2.27.1	6 / 5	2026-02-27
2.27.0	6 / 5	2026-02-12
2.26.2	6 / 5	2026-02-03
2.26.1	6 / 5	2026-01-27
2.26.0	6 / 5	2026-01-15
2.25.0	6 / 2	2025-12-18
2.24.5	6 / 2	2025-12-09
2.24.4	6 / 2	2025-12-01
2.24.3	6 / 2	2025-11-28
2.24.2	6 / 2	2025-11-26
2.24.1	6 / 2	2025-11-21
2.24.0	6 / 2	2025-11-20
2.23.1	6 / 2	2025-10-27
2.23.0	6 / 2	2025-10-23
2.22.1	6 / 2	2025-10-14
2.22.0	6 / 2	2025-09-25
2.21.2	6 / 2	2025-09-10
2.21.1	6 / 2	2025-08-28
2.21.0	6 / 2	2025-08-28
2.20.0	6 / 2	2025-07-31
2.19.1	6 / 2	2025-07-22
2.19.0	6 / 2	2025-07-03
2.18.0	6 / 2	2025-06-05
2.17.0	5 / 2	2025-05-08

v2.31.0

1 finding

LOW No provenance attestation provenance

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

v2.30.1

1 finding

LOW No provenance attestation provenance

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

v2.30.0

1 finding

LOW No provenance attestation provenance

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

v2.29.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.

v2.29.0

1 finding

LOW No provenance attestation provenance

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

v2.28.1

1 finding

LOW No provenance attestation provenance

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

v2.28.0

2 findings

HIGH Publisher changed: hardillb → flowfuse-user (on 2026-03-12) provenance

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

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: hardillb → flowfuse-user (on 2026-02-27, known maintainer) provenance

This version was published by a different npm account (flowfuse-user) than the most recent previously approved version (hardillb) on 2026-02-27, but flowfuse-user is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.27.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: hardillb → flowfuse-user (on 2026-02-12, known maintainer) provenance

This version was published by a different npm account (flowfuse-user) than the most recent previously approved version (hardillb) on 2026-02-12, but flowfuse-user is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.26.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: hardillb → flowfuse-user (on 2026-02-03, known maintainer) provenance

This version was published by a different npm account (flowfuse-user) than the most recent previously approved version (hardillb) on 2026-02-03, but flowfuse-user is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.26.1

1 finding

LOW No provenance attestation provenance

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

v2.26.0

1 finding

LOW No provenance attestation provenance

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

v2.25.0

1 finding

LOW No provenance attestation provenance

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

v2.24.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: flowfuse-user → hardillb (on 2025-12-09, known maintainer) provenance

This version was published by a different npm account (hardillb) than the most recent previously approved version (flowfuse-user) on 2025-12-09, but hardillb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.24.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: flowfuse-user → hardillb (on 2025-12-01, known maintainer) provenance

This version was published by a different npm account (hardillb) than the most recent previously approved version (flowfuse-user) on 2025-12-01, but hardillb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.24.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: flowfuse-user → hardillb (on 2025-11-28, known maintainer) provenance

This version was published by a different npm account (hardillb) than the most recent previously approved version (flowfuse-user) on 2025-11-28, but hardillb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.24.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: flowfuse-user → hardillb (on 2025-11-26, known maintainer) provenance

This version was published by a different npm account (hardillb) than the most recent previously approved version (flowfuse-user) on 2025-11-26, but hardillb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.24.1

1 finding

LOW No provenance attestation provenance

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

v2.24.0

1 finding

LOW No provenance attestation provenance

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

v2.23.1

1 finding

LOW No provenance attestation provenance

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

v2.23.0

1 finding

LOW No provenance attestation provenance

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

v2.22.1

1 finding

LOW No provenance attestation provenance

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

v2.22.0

1 finding

LOW No provenance attestation provenance

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

v2.21.2

1 finding

LOW No provenance attestation provenance

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

v2.21.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.

v2.21.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.20.0

1 finding

LOW No provenance attestation provenance

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

v2.19.1

1 finding

LOW No provenance attestation provenance

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

v2.19.0

1 finding

LOW No provenance attestation provenance

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

v2.18.0

1 finding

LOW No provenance attestation provenance

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

v2.17.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.