@khanacademy/wonder-blocks-pill
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 |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation confirms legitimate CI/CD publishing pipeline. | ai | |
| provenance | publisher-changed | AI (provenance): Khan Academy migrated to GitHub Actions publishing with SLSA attestation; this is a documented CI/CD transition, not a compromise. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-link | AI (dependencies): First-party sibling package from same Khan Academy monorepo. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-styles | AI (dependencies): First-party sibling package from same Khan Academy monorepo. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-clickable | AI (dependencies): First-party sibling package from same Khan Academy monorepo. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-typography | AI (dependencies): First-party sibling package from same Khan Academy monorepo. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-tokens | AI (dependencies): First-party sibling package from same Khan Academy monorepo. | ai | |
| dependencies | unvetted-dep:@khanacademy/wonder-blocks-core | AI (dependencies): First-party sibling package from same Khan Academy monorepo; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@khanacademy/wonder-blocks-link | AI (phantom-deps): Same-org monorepo sibling; declared-but-not-directly-imported is a stable false positive for this package. | ai |
Versions (showing 82 of 82)
| Version | Deps | Published |
|---|---|---|
| 3.1.72 | 6 / 1 | |
| 3.1.71 | 6 / 1 | |
| 3.1.70 | 6 / 1 | |
| 3.1.69 | 6 / 1 | |
| 3.1.68 | 6 / 1 | |
| 3.1.67 | 6 / 1 | |
| 3.1.66 | 6 / 1 | |
| 3.1.65 | 6 / 1 | |
| 3.1.64 | 6 / 1 | |
| 3.1.63 | 6 / 1 | |
| 3.1.62 | 6 / 1 | |
| 3.1.61 | 6 / 1 | |
| 3.1.60 | 6 / 1 | |
| 3.1.59 | 6 / 1 | |
| 3.1.58 | 6 / 1 | |
| 3.1.57 | 6 / 1 | |
| 3.1.56 | 6 / 1 | |
| 3.1.55 | 6 / 1 | |
| 3.1.54 | 6 / 1 | |
| 3.1.53 | 6 / 1 | |
| 3.1.52 | 6 / 1 | |
| 3.1.51 | 6 / 1 | |
| 3.1.50 | 6 / 1 | |
| 3.1.49 | 6 / 1 | |
| 3.1.48 | 6 / 1 | |
| 3.1.47 | 6 / 1 | |
| 3.1.46 | 6 / 1 | |
| 3.1.45 | 6 / 1 | |
| 3.1.44 | 6 / 1 | |
| 3.1.43 | 6 / 1 | |
| 3.1.42 | 6 / 1 | |
| 3.1.41 | 6 / 1 | |
| 3.1.40 | 6 / 1 | |
| 3.1.39 | 6 / 1 | |
| 3.1.38 | 6 / 1 | |
| 3.1.37 | 6 / 1 | |
| 3.1.36 | 6 / 1 | |
| 3.1.35 | 6 / 1 | |
| 3.1.34 | 6 / 1 | |
| 3.1.33 | 6 / 1 | |
| 3.1.32 | 6 / 1 | |
| 3.1.31 | 6 / 1 | |
| 3.1.30 | 6 / 1 | |
| 3.1.29 | 6 / 1 | |
| 3.1.28 | 6 / 1 | |
| 3.1.27 | 6 / 1 | |
| 3.1.26 | 5 / 1 | |
| 3.1.25 | 5 / 1 | |
| 3.1.24 | 5 / 1 | |
| 3.1.23 | 5 / 1 | |
| 3.1.22 | 5 / 1 | |
| 3.1.21 | 5 / 1 | |
| 3.1.20 | 5 / 1 | |
| 3.1.19 | 5 / 1 | |
| 3.1.18 | 5 / 1 | |
| 3.1.17 | 5 / 1 | |
| 3.1.16 | 5 / 1 | |
| 3.1.15 | 5 / 1 | |
| 3.1.14 | 5 / 1 | |
| 3.1.13 | 5 / 1 | |
| 3.1.12 | 5 / 1 | |
| 3.1.11 | 5 / 1 | |
| 3.1.10 | 6 / 1 | |
| 3.1.9 | 6 / 1 | |
| 3.1.8 | 6 / 1 | |
| 3.1.7 | 6 / 1 | |
| 3.1.6 | 6 / 1 | |
| 3.1.5 | 6 / 1 | |
| 3.1.4 | 6 / 1 | |
| 3.1.3 | 6 / 1 | |
| 3.1.2 | 6 / 1 | |
| 3.1.1 | 6 / 1 | |
| 3.1.0 | 6 / 1 | |
| 3.0.8 | 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.1.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
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.8
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.