@khanacademy/wonder-blocks-popover
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-core | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-modal | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-styles | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-tokens | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-tooltip | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-typography | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-icon-button | AI (dependencies): First-party KA monorepo sibling; not an independent third-party risk. | ai |
Versions (showing 69 of 69)
| Version | Deps | Published |
|---|---|---|
| 6.3.3 | 7 / 1 | |
| 6.3.2 | 7 / 1 | |
| 6.3.1 | 7 / 1 | |
| 6.3.0 | 7 / 1 | |
| 6.2.5 | 7 / 1 | |
| 6.2.4 | 7 / 1 | |
| 6.2.3 | 7 / 1 | |
| 6.2.2 | 7 / 1 | |
| 6.2.1 | 7 / 1 | |
| 6.2.0 | 7 / 1 | |
| 6.1.57 | 7 / 1 | |
| 6.1.56 | 7 / 1 | |
| 6.1.55 | 7 / 1 | |
| 6.1.54 | 7 / 1 | |
| 6.1.53 | 7 / 1 | |
| 6.1.52 | 7 / 1 | |
| 6.1.51 | 7 / 1 | |
| 6.1.50 | 7 / 1 | |
| 6.1.49 | 7 / 1 | |
| 6.1.48 | 7 / 1 | |
| 6.1.47 | 7 / 1 | |
| 6.1.46 | 7 / 1 | |
| 6.1.45 | 7 / 1 | |
| 6.1.44 | 7 / 1 | |
| 6.1.43 | 7 / 1 | |
| 6.1.42 | 7 / 1 | |
| 6.1.41 | 7 / 1 | |
| 6.1.40 | 7 / 1 | |
| 6.1.39 | 7 / 1 | |
| 6.1.38 | 7 / 1 | |
| 6.1.37 | 7 / 1 | |
| 6.1.36 | 7 / 1 | |
| 6.1.35 | 7 / 1 | |
| 6.1.34 | 7 / 1 | |
| 6.1.33 | 7 / 1 | |
| 6.1.32 | 7 / 1 | |
| 6.1.31 | 7 / 1 | |
| 6.1.30 | 7 / 1 | |
| 6.1.29 | 7 / 1 | |
| 6.1.28 | 7 / 1 | |
| 6.1.27 | 7 / 1 | |
| 6.1.26 | 7 / 1 | |
| 6.1.25 | 7 / 1 | |
| 6.1.24 | 7 / 1 | |
| 6.1.23 | 7 / 1 | |
| 6.1.22 | 7 / 1 | |
| 6.1.21 | 7 / 1 | |
| 6.1.20 | 7 / 1 | |
| 6.1.19 | 7 / 1 | |
| 6.1.18 | 7 / 1 | |
| 6.1.17 | 7 / 1 | |
| 6.1.16 | 7 / 1 | |
| 6.1.15 | 7 / 1 | |
| 6.1.14 | 7 / 1 | |
| 6.1.13 | 7 / 1 | |
| 6.1.12 | 7 / 1 | |
| 6.1.11 | 7 / 1 | |
| 6.1.10 | 7 / 1 | |
| 6.1.9 | 7 / 1 | |
| 6.1.8 | 7 / 1 | |
| 6.1.7 | 7 / 1 | |
| 6.1.6 | 7 / 1 | |
| 6.1.5 | 7 / 1 | |
| 6.1.4 | 7 / 1 | |
| 6.1.3 | 7 / 1 | |
| 6.1.2 | 7 / 1 | |
| 6.1.1 | 7 / 1 | |
| 6.1.0 | 7 / 1 | |
| 6.0.8 | 7 / 1 |
v6.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.