@khanacademy/wonder-blocks-styles
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-tokens | AI (dependencies): Same-org monorepo sibling; stable false positive for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.2.52 | 1 / 1 | |
| 0.2.51 | 1 / 1 | |
| 0.2.50 | 1 / 1 | |
| 0.2.49 | 1 / 1 | |
| 0.2.48 | 1 / 1 | |
| 0.2.47 | 1 / 1 | |
| 0.2.46 | 1 / 1 | |
| 0.2.45 | 1 / 1 | |
| 0.2.44 | 1 / 1 | |
| 0.2.43 | 1 / 1 | |
| 0.2.42 | 1 / 1 | |
| 0.2.41 | 1 / 1 | |
| 0.2.40 | 1 / 1 | |
| 0.2.39 | 1 / 1 | |
| 0.2.38 | 1 / 1 | |
| 0.2.37 | 1 / 1 | |
| 0.2.36 | 1 / 1 | |
| 0.2.35 | 1 / 1 | |
| 0.2.34 | 1 / 1 | |
| 0.2.33 | 1 / 1 | |
| 0.2.32 | 1 / 1 | |
| 0.2.31 | 1 / 1 | |
| 0.2.30 | 1 / 1 | |
| 0.2.29 | 1 / 1 | |
| 0.2.28 | 1 / 1 | |
| 0.2.27 | 1 / 1 | |
| 0.2.26 | 1 / 1 | |
| 0.2.25 | 1 / 1 | |
| 0.2.24 | 1 / 1 | |
| 0.2.23 | 1 / 1 | |
| 0.2.22 | 1 / 1 | |
| 0.2.21 | 1 / 1 | |
| 0.2.20 | 1 / 1 | |
| 0.2.19 | 1 / 1 | |
| 0.2.18 | 1 / 1 | |
| 0.2.17 | 1 / 1 | |
| 0.2.16 | 1 / 1 | |
| 0.2.15 | 1 / 1 | |
| 0.2.14 | 1 / 1 | |
| 0.2.13 | 1 / 1 | |
| 0.2.12 | 1 / 1 | |
| 0.2.11 | 1 / 1 | |
| 0.2.10 | 1 / 1 | |
| 0.2.9 | 1 / 1 | |
| 0.2.8 | 1 / 1 | |
| 0.2.7 | 1 / 1 | |
| 0.2.6 | 2 / 1 | |
| 0.2.5 | 2 / 1 | |
| 0.2.4 | 2 / 1 | |
| 0.2.3 | 2 / 1 | |
| 0.2.2 | 2 / 1 |
v0.2.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.