@khanacademy/wonder-blocks-switch
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 3.4.8 | 5 / 1 | |
| 3.4.7 | 5 / 1 | |
| 3.4.6 | 5 / 1 | |
| 3.4.5 | 5 / 1 | |
| 3.4.4 | 5 / 1 | |
| 3.4.3 | 5 / 1 | |
| 3.4.2 | 5 / 1 | |
| 3.4.1 | 5 / 1 | |
| 3.4.0 | 5 / 1 | |
| 3.3.34 | 5 / 1 | |
| 3.3.33 | 5 / 1 | |
| 3.3.32 | 5 / 1 | |
| 3.3.31 | 5 / 1 | |
| 3.3.30 | 5 / 1 | |
| 3.3.29 | 5 / 1 | |
| 3.3.28 | 5 / 1 | |
| 3.3.27 | 5 / 1 | |
| 3.3.26 | 5 / 1 | |
| 3.3.25 | 5 / 1 | |
| 3.3.24 | 5 / 1 | |
| 3.3.23 | 5 / 1 | |
| 3.3.22 | 5 / 1 | |
| 3.3.21 | 5 / 1 | |
| 3.3.20 | 5 / 1 | |
| 3.3.19 | 5 / 1 | |
| 3.3.18 | 5 / 1 | |
| 3.3.17 | 5 / 1 | |
| 3.3.16 | 5 / 1 | |
| 3.3.15 | 5 / 1 | |
| 3.3.14 | 5 / 1 | |
| 3.3.13 | 5 / 1 | |
| 3.3.12 | 5 / 1 | |
| 3.3.11 | 5 / 1 | |
| 3.3.10 | 5 / 1 | |
| 3.3.9 | 5 / 1 | |
| 3.3.8 | 5 / 1 | |
| 3.3.7 | 5 / 1 | |
| 3.3.6 | 5 / 1 | |
| 3.3.5 | 5 / 1 | |
| 3.3.4 | 5 / 1 | |
| 3.3.3 | 5 / 1 | |
| 3.3.2 | 5 / 1 | |
| 3.3.1 | 5 / 1 | |
| 3.3.0 | 5 / 1 | |
| 3.2.10 | 5 / 1 | |
| 3.2.9 | 5 / 1 | |
| 3.2.8 | 5 / 1 | |
| 3.2.7 | 5 / 1 | |
| 3.2.6 | 5 / 1 | |
| 3.2.5 | 5 / 1 | |
| 3.2.4 | 5 / 1 | |
| 3.2.3 | 5 / 1 | |
| 3.2.2 | 6 / 1 | |
| 3.2.1 | 6 / 1 | |
| 3.2.0 | 6 / 1 | |
| 3.1.8 | 5 / 1 | |
| 3.1.7 | 5 / 1 | |
| 3.1.6 | 5 / 1 | |
| 3.1.5 | 5 / 1 | |
| 3.1.4 | 5 / 1 | |
| 3.1.3 | 5 / 1 | |
| 3.1.2 | 5 / 1 | |
| 3.1.1 | 5 / 1 | |
| 3.1.0 | 5 / 1 | |
| 3.0.7 | 5 / 1 | |
| 3.0.6 | 5 / 1 | |
| 3.0.5 | 5 / 1 | |
| 3.0.4 | 5 / 1 | |
| 3.0.3 | 5 / 1 | |
| 3.0.2 | 5 / 1 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 |
v3.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.