@khanacademy/wonder-blocks-tooltip
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Empty description is a known pattern for this monorepo package; not indicative of malicious intent. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 5 / 1 | |
| 4.1.85 | 5 / 1 | |
| 4.1.84 | 5 / 1 | |
| 4.1.83 | 5 / 1 | |
| 4.1.82 | 5 / 1 | |
| 4.1.81 | 5 / 1 | |
| 4.1.80 | 5 / 1 | |
| 4.1.79 | 5 / 1 | |
| 4.1.78 | 5 / 1 | |
| 4.1.77 | 5 / 1 | |
| 4.1.76 | 5 / 1 | |
| 4.1.75 | 5 / 1 | |
| 4.1.74 | 5 / 1 | |
| 4.1.73 | 5 / 1 | |
| 4.1.72 | 5 / 1 | |
| 4.1.71 | 5 / 1 | |
| 4.1.70 | 5 / 1 | |
| 4.1.69 | 5 / 1 | |
| 4.1.68 | 5 / 1 | |
| 4.1.67 | 5 / 1 | |
| 4.1.66 | 5 / 1 | |
| 4.1.65 | 5 / 1 | |
| 4.1.64 | 5 / 1 | |
| 4.1.63 | 5 / 1 | |
| 4.1.62 | 5 / 1 | |
| 4.1.61 | 5 / 1 | |
| 4.1.60 | 5 / 1 | |
| 4.1.59 | 5 / 1 | |
| 4.1.58 | 5 / 1 | |
| 4.1.57 | 5 / 1 | |
| 4.1.56 | 5 / 1 | |
| 4.1.55 | 5 / 1 | |
| 4.1.54 | 5 / 1 | |
| 4.1.53 | 5 / 1 | |
| 4.1.52 | 5 / 1 | |
| 4.1.51 | 5 / 1 | |
| 4.1.50 | 5 / 1 | |
| 4.1.49 | 5 / 1 | |
| 4.1.48 | 5 / 1 | |
| 4.1.47 | 5 / 1 | |
| 4.1.46 | 5 / 1 | |
| 4.1.45 | 5 / 1 | |
| 4.1.44 | 5 / 1 | |
| 4.1.43 | 5 / 1 | |
| 4.1.42 | 5 / 1 | |
| 4.1.41 | 5 / 1 | |
| 4.1.40 | 5 / 1 | |
| 4.1.39 | 5 / 1 | |
| 4.1.38 | 5 / 1 | |
| 4.1.37 | 5 / 1 | |
| 4.1.36 | 5 / 1 | |
| 4.1.35 | 5 / 1 | |
| 4.1.34 | 5 / 1 | |
| 4.1.33 | 5 / 1 | |
| 4.1.32 | 5 / 1 | |
| 4.1.31 | 5 / 1 | |
| 4.1.30 | 5 / 1 | |
| 4.1.29 | 5 / 1 | |
| 4.1.28 | 5 / 1 | |
| 4.1.27 | 5 / 1 | |
| 4.1.26 | 5 / 1 | |
| 4.1.25 | 5 / 1 | |
| 4.1.24 | 5 / 1 | |
| 4.1.23 | 5 / 1 | |
| 4.1.22 | 5 / 1 | |
| 4.1.21 | 5 / 1 | |
| 4.1.20 | 5 / 1 | |
| 4.1.19 | 5 / 1 | |
| 4.1.18 | 5 / 1 | |
| 4.1.17 | 5 / 1 | |
| 4.1.16 | 5 / 1 | |
| 4.1.15 | 5 / 1 | |
| 4.1.14 | 5 / 1 | |
| 4.1.13 | 5 / 1 | |
| 4.1.12 | 6 / 1 | |
| 4.1.11 | 6 / 1 | |
| 4.1.10 | 6 / 1 | |
| 4.1.9 | 6 / 1 | |
| 4.1.8 | 6 / 1 | |
| 4.1.7 | 6 / 1 | |
| 4.1.6 | 6 / 1 | |
| 4.1.5 | 6 / 1 | |
| 4.1.4 | 6 / 1 | |
| 4.1.3 | 6 / 1 | |
| 4.1.2 | 6 / 1 | |
| 4.1.1 | 6 / 1 | |
| 4.1.0 | 6 / 1 | |
| 4.0.7 | 6 / 1 | |
| 4.0.6 | 6 / 1 | |
| 4.0.5 | 6 / 1 | |
| 4.0.4 | 6 / 1 | |
| 4.0.3 | 6 / 1 | |
| 4.0.2 | 6 / 1 | |
| 4.0.1 | 6 / 1 | |
| 4.0.0 | 6 / 1 |
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.85
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.84
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.83
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.