@launchpad-ui/modal
An element that presents users information and actions over a page.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@launchpad-ui/tokens | AI (phantom-deps): Same-org monorepo package; tokens likely consumed via CSS/transitive path, not direct JS import. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.21.17 | 7 / 3 | |
| 0.21.16 | 7 / 3 | |
| 0.21.15 | 7 / 3 | |
| 0.21.14 | 7 / 4 | |
| 0.21.11 | 7 / 4 | |
| 0.21.10 | 7 / 4 | |
| 0.21.9 | 7 / 4 | |
| 0.21.8 | 7 / 4 | |
| 0.21.7 | 7 / 4 | |
| 0.21.6 | 7 / 4 | |
| 0.21.5 | 7 / 4 | |
| 0.21.4 | 7 / 4 | |
| 0.21.3 | 7 / 4 | |
| 0.21.2 | 7 / 4 | |
| 0.21.1 | 7 / 4 | |
| 0.21.0 | 7 / 4 | |
| 0.20.0 | 7 / 4 | |
| 0.19.0 | 7 / 4 | |
| 0.18.4 | 7 / 4 | |
| 0.18.3 | 7 / 4 | |
| 0.18.2 | 7 / 4 | |
| 0.18.1 | 7 / 4 | |
| 0.18.0 | 7 / 4 | |
| 0.17.81 | 9 / 2 | |
| 0.17.80 | 9 / 2 | |
| 0.17.79 | 9 / 2 | |
| 0.17.78 | 9 / 2 | |
| 0.17.77 | 9 / 2 | |
| 0.17.76 | 9 / 2 | |
| 0.17.75 | 9 / 2 | |
| 0.17.74 | 9 / 2 | |
| 0.17.73 | 9 / 2 | |
| 0.17.72 | 9 / 2 | |
| 0.17.71 | 9 / 2 | |
| 0.17.70 | 9 / 2 | |
| 0.17.69 | 9 / 2 | |
| 0.17.68 | 9 / 2 | |
| 0.17.67 | 9 / 2 | |
| 0.17.66 | 9 / 2 | |
| 0.17.65 | 9 / 2 | |
| 0.17.64 | 9 / 2 | |
| 0.17.63 | 9 / 2 | |
| 0.17.62 | 9 / 2 | |
| 0.17.61 | 9 / 2 | |
| 0.17.60 | 9 / 2 | |
| 0.17.59 | 9 / 2 | |
| 0.17.58 | 9 / 2 | |
| 0.17.57 | 9 / 2 | |
| 0.17.56 | 9 / 2 | |
| 0.17.55 | 9 / 2 | |
| 0.17.54 | 9 / 2 | |
| 0.17.53 | 9 / 2 | |
| 0.17.52 | 9 / 2 | |
| 0.17.51 | 9 / 2 | |
| 0.17.50 | 9 / 2 | |
| 0.17.49 | 9 / 2 | |
| 0.17.48 | 9 / 2 | |
| 0.17.47 | 9 / 2 | |
| 0.17.46 | 9 / 2 | |
| 0.17.45 | 9 / 2 | |
| 0.17.44 | 9 / 2 | |
| 0.17.43 | 9 / 2 | |
| 0.17.42 | 9 / 2 | |
| 0.17.41 | 9 / 2 | |
| 0.17.40 | 9 / 2 | |
| 0.17.39 | 9 / 2 | |
| 0.17.38 | 9 / 2 | |
| 0.17.37 | 9 / 2 | |
| 0.17.36 | 9 / 2 | |
| 0.17.35 | 9 / 2 | |
| 0.17.34 | 9 / 2 | |
| 0.17.33 | 9 / 2 | |
| 0.17.32 | 9 / 2 | |
| 0.17.31 | 9 / 2 | |
| 0.17.30 | 9 / 2 | |
| 0.17.29 | 9 / 2 | |
| 0.17.28 | 9 / 2 | |
| 0.17.27 | 9 / 2 | |
| 0.17.26 | 9 / 2 |
v0.21.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.