@flowfuse/driver-kubernetes
Kubernetes driver for FlowFuse
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): hardillb is a known FlowFuse org contributor with clean track record; publisher rotation within org is expected. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 2.32.0 | 6 / 5 | |
| 2.31.3 | 6 / 5 | |
| 2.31.2 | 6 / 5 | |
| 2.31.1 | 6 / 5 | |
| 2.31.0 | 6 / 5 | |
| 2.30.1 | 6 / 5 | |
| 2.30.0 | 6 / 5 | |
| 2.29.1 | 6 / 5 | |
| 2.29.0 | 6 / 5 | |
| 2.28.1 | 5 / 5 | |
| 2.28.0 | 5 / 5 | |
| 2.27.1 | 5 / 5 | |
| 2.27.0 | 5 / 5 | |
| 2.26.2 | 5 / 5 | |
| 2.26.1 | 5 / 5 | |
| 2.26.0 | 5 / 5 | |
| 2.25.0 | 5 / 2 | |
| 2.24.5 | 5 / 2 | |
| 2.24.4 | 5 / 2 | |
| 2.24.3 | 5 / 2 | |
| 2.24.2 | 5 / 2 | |
| 2.24.1 | 5 / 2 | |
| 2.24.0 | 5 / 2 | |
| 2.23.1 | 5 / 2 | |
| 2.23.0 | 5 / 2 | |
| 2.22.1 | 5 / 2 | |
| 2.22.0 | 5 / 2 | |
| 2.21.2 | 5 / 2 | |
| 2.21.1 | 5 / 2 | |
| 2.21.0 | 5 / 2 | |
| 2.20.0 | 5 / 2 | |
| 2.19.1 | 5 / 2 | |
| 2.19.0 | 5 / 2 | |
| 2.18.0 | 5 / 2 | |
| 2.17.0 | 5 / 2 | |
| 2.16.0 | 5 / 2 | |
| 2.15.0 | 5 / 2 | |
| 2.14.1 | 5 / 2 | |
| 2.14.0 | 5 / 2 | |
| 2.13.0 | 5 / 2 | |
| 2.12.0 | 5 / 2 | |
| 2.11.0 | 5 / 2 | |
| 2.10.0 | 5 / 2 | |
| 2.9.0 | 5 / 2 | |
| 2.8.0 | 5 / 2 | |
| 2.7.0 | 4 / 2 | |
| 2.6.0 | 4 / 2 | |
| 2.5.0 | 3 / 2 | |
| 2.4.0 | 3 / 2 |
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
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 (flowfuse-user) than the most recent previously approved version (knolleary) on 2025-04-10, 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.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.