@khanacademy/wonder-blocks-modal
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): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-layout | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-styles | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-timing | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-tokens | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-announcer | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-typography | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-breadcrumbs | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-icon-button | AI (dependencies): Same-org sibling package from Khan Academy's wonder-blocks monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@khanacademy/wonder-blocks-layout | AI (phantom-deps): Same-org sibling; may be used indirectly or re-exported; stable false positive for this monorepo package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 8.7.2 | 9 / 2 | |
| 8.7.1 | 9 / 2 | |
| 8.7.0 | 9 / 2 | |
| 8.6.5 | 9 / 2 | |
| 8.6.4 | 9 / 2 | |
| 8.6.3 | 9 / 2 | |
| 8.6.2 | 9 / 2 | |
| 8.6.1 | 9 / 2 | |
| 8.6.0 | 9 / 2 | |
| 8.5.17 | 8 / 2 | |
| 8.5.16 | 8 / 2 | |
| 8.5.15 | 8 / 2 | |
| 8.5.14 | 8 / 2 | |
| 8.5.13 | 8 / 2 | |
| 8.5.12 | 8 / 2 | |
| 8.5.11 | 8 / 2 | |
| 8.5.10 | 8 / 2 | |
| 8.5.9 | 8 / 2 | |
| 8.5.8 | 8 / 2 | |
| 8.5.7 | 8 / 2 | |
| 8.5.6 | 8 / 2 | |
| 8.5.5 | 8 / 2 | |
| 8.5.4 | 8 / 2 | |
| 8.5.3 | 8 / 2 | |
| 8.5.2 | 8 / 2 | |
| 8.5.1 | 8 / 2 | |
| 8.5.0 | 8 / 2 | |
| 8.4.6 | 8 / 2 | |
| 8.4.5 | 8 / 2 | |
| 8.4.4 | 8 / 2 | |
| 8.4.3 | 8 / 2 | |
| 8.4.2 | 8 / 2 | |
| 8.4.1 | 8 / 2 | |
| 8.4.0 | 8 / 2 | |
| 8.3.1 | 8 / 2 | |
| 8.3.0 | 8 / 2 | |
| 8.2.3 | 8 / 2 | |
| 8.2.2 | 8 / 2 | |
| 8.2.1 | 8 / 2 | |
| 8.2.0 | 8 / 2 | |
| 8.1.9 | 8 / 2 | |
| 8.1.8 | 8 / 2 | |
| 8.1.7 | 8 / 2 | |
| 8.1.6 | 8 / 2 | |
| 8.1.5 | 8 / 2 | |
| 8.1.4 | 8 / 2 | |
| 8.1.3 | 8 / 2 | |
| 8.1.2 | 8 / 2 | |
| 8.1.1 | 8 / 2 | |
| 8.1.0 | 8 / 2 | |
| 8.0.1 | 8 / 2 |
v8.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.