@flowfuse/nr-launcher
FlowFuse Launcher for running Node-RED
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@flowfuse/nr-subflow-export | AI (dependencies): First-party FlowFuse org package. | ai | |
| dependencies | unvetted-dep:@flowfuse/nr-file-nodes | AI (dependencies): First-party FlowFuse org package. | ai | |
| dependencies | unvetted-dep:@flowfuse/nr-project-nodes | AI (dependencies): First-party FlowFuse org package. | ai | |
| dependencies | unvetted-dep:@node-red/util | AI (dependencies): Core Node-RED utility package, expected dependency. | ai | |
| npm-metadata | url-dep:@flowforge/file-server | AI (npm-metadata): Dev-only dependency pointing to FlowFuse's own repo. | ai | |
| provenance | publisher-changed | AI (provenance): New account has strong approved track record; likely org CI account rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Coincides with trusted publisher change, no other risk signal. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-project-nodes | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-assistant | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-file-nodes | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-mqtt-nodes | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-tables-nodes | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher. | ai | |
| phantom-deps | phantom-dep:@flowfuse/nr-subflow-export | AI (phantom-deps): FlowFuse org plugin injected at runtime by the launcher. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is declared as a direct dependency and used via express-ws; phantom-dep is a false positive here. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Launcher package; spawning Node-RED child processes is core functionality. | ai | |
| bogus-package | bogus-package | AI (bogus-package): FlowFuse org package; knolleary is the Node-RED creator, mass-production signal is a false positive here. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 default URL in a JSDoc comment for localhost file store; not a network exfiltration risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Reads node-red package.json to extract version string; not arbitrary code loading. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Spawns npm install and Node-RED process — expected for a launcher. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 2.32.1 | 23 / 11 | |
| 2.32.0 | 24 / 11 | |
| 2.31.3 | 24 / 11 | |
| 2.31.2 | 24 / 11 | |
| 2.31.1 | 24 / 11 | |
| 2.31.0 | 24 / 11 | |
| 2.30.1 | 24 / 11 | |
| 2.30.0 | 24 / 11 | |
| 2.29.1 | 24 / 11 | |
| 2.29.0 | 24 / 11 | |
| 2.28.1 | 24 / 11 | |
| 2.28.0 | 24 / 11 | |
| 2.27.1 | 24 / 11 | |
| 2.27.0 | 24 / 11 | |
| 2.26.2 | 24 / 11 | |
| 2.26.1 | 24 / 12 | |
| 2.26.0 | 24 / 12 | |
| 2.25.0 | 24 / 10 | |
| 2.24.5 | 24 / 10 | |
| 2.24.4 | 24 / 10 | |
| 2.24.3 | 24 / 10 | |
| 2.24.2 | 24 / 10 | |
| 2.24.1 | 24 / 10 | |
| 2.24.0 | 24 / 10 | |
| 2.23.1 | 24 / 10 | |
| 2.23.0 | 24 / 10 | |
| 2.22.1 | 24 / 10 | |
| 2.22.0 | 24 / 10 | |
| 2.21.2 | 24 / 10 | |
| 2.21.1 | 24 / 10 | |
| 2.21.0 | 24 / 10 | |
| 2.20.0 | 22 / 10 | |
| 2.19.1 | 21 / 10 | |
| 2.19.0 | 21 / 10 | |
| 2.18.0 | 20 / 10 | |
| 2.17.0 | 19 / 10 | |
| 2.16.0 | 19 / 10 | |
| 2.15.0 | 19 / 10 | |
| 2.14.1 | 19 / 10 | |
| 2.14.0 | 19 / 10 | |
| 2.13.0 | 19 / 10 | |
| 2.12.0 | 19 / 10 | |
| 2.11.0 | 18 / 10 | |
| 2.10.0 | 18 / 10 | |
| 2.9.0 | 18 / 10 | |
| 2.8.0 | 18 / 10 | |
| 2.7.0 | 17 / 10 | |
| 2.6.0 | 17 / 10 | |
| 2.5.1 | 16 / 9 | |
| 2.5.0 | 16 / 9 | |
| 2.4.0 | 16 / 9 |
v2.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.