miniflare
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 4.20260504.0 | 6 / 49 | |
| 4.20260430.0 | 6 / 49 | |
| 4.20260426.0 | 6 / 49 | |
| 4.20250803.0 | 12 / 45 | |
| 4.20250730.0 | 12 / 44 | |
| 4.20250726.0 | 12 / 44 | |
| 4.20250712.2 | 12 / 44 | |
| 4.20250712.1 | 12 / 44 | |
| 4.20250712.0 | 12 / 44 | |
| 4.20250709.0 | 12 / 44 | |
| 4.20250705.0 | 12 / 44 | |
| 4.20250617.5 | 12 / 43 | |
| 4.20250617.4 | 12 / 43 | |
| 4.20250617.3 | 12 / 43 | |
| 4.20250617.2 | 12 / 43 | |
| 4.20250617.1 | 12 / 43 | |
| 4.20250617.0 | 12 / 43 | |
| 4.20250612.0 | 12 / 43 | |
| 4.20250604.1 | 12 / 43 | |
| 4.20250604.0 | 12 / 42 | |
| 4.20250525.1 | 12 / 42 | |
| 4.20250525.0 | 12 / 40 | |
| 4.20250523.0 | 12 / 40 | |
| 4.20250508.3 | 12 / 40 | |
| 4.20250508.2 | 11 / 40 | |
| 4.20250508.1 | 11 / 40 | |
| 4.20250508.0 | 11 / 40 | |
| 4.20250507.0 | 11 / 40 | |
| 4.20250428.1 | 11 / 40 | |
| 4.20250428.0 | 11 / 40 | |
| 3.20250718.3 | 11 / 38 |
v4.20260504.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20260430.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20260426.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.20250803.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250730.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250726.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250712.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250712.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250712.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250709.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250705.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250617.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250612.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250604.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250604.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250525.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250525.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250523.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250508.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250508.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250508.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20250508.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20250507.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20250428.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20250428.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20250718.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.