@launchpad-ui/dropdown
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 sibling dep; may be used transitively or in CSS/type-only imports not caught by the heuristic. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 0.10.17 | 5 / 4 | |
| 0.10.16 | 5 / 4 | |
| 0.10.15 | 5 / 4 | |
| 0.10.14 | 5 / 4 | |
| 0.10.11 | 5 / 4 | |
| 0.10.10 | 5 / 4 | |
| 0.10.9 | 5 / 4 | |
| 0.10.8 | 5 / 4 | |
| 0.10.7 | 5 / 4 | |
| 0.10.6 | 5 / 4 | |
| 0.10.5 | 5 / 4 | |
| 0.10.4 | 5 / 4 | |
| 0.10.3 | 5 / 4 | |
| 0.10.2 | 5 / 4 | |
| 0.10.1 | 5 / 4 | |
| 0.10.0 | 5 / 4 | |
| 0.9.0 | 5 / 4 | |
| 0.8.0 | 5 / 4 | |
| 0.7.4 | 5 / 4 | |
| 0.7.3 | 5 / 4 | |
| 0.7.2 | 5 / 4 | |
| 0.7.1 | 5 / 4 | |
| 0.7.0 | 5 / 4 | |
| 0.6.153 | 6 / 3 | |
| 0.6.152 | 6 / 3 | |
| 0.6.151 | 6 / 3 | |
| 0.6.150 | 6 / 3 | |
| 0.6.149 | 6 / 3 | |
| 0.6.148 | 6 / 3 | |
| 0.6.147 | 6 / 3 | |
| 0.6.146 | 6 / 3 | |
| 0.6.145 | 6 / 3 | |
| 0.6.144 | 6 / 3 | |
| 0.6.143 | 6 / 3 | |
| 0.6.142 | 6 / 3 | |
| 0.6.141 | 6 / 3 | |
| 0.6.140 | 6 / 3 | |
| 0.6.139 | 6 / 3 | |
| 0.6.138 | 6 / 3 | |
| 0.6.137 | 6 / 3 | |
| 0.6.136 | 6 / 3 | |
| 0.6.135 | 6 / 3 | |
| 0.6.134 | 6 / 2 | |
| 0.6.133 | 6 / 2 | |
| 0.6.132 | 6 / 2 | |
| 0.6.131 | 6 / 2 | |
| 0.6.130 | 6 / 2 | |
| 0.6.129 | 6 / 2 | |
| 0.6.128 | 6 / 2 | |
| 0.6.127 | 6 / 2 | |
| 0.6.126 | 6 / 2 | |
| 0.6.125 | 6 / 2 | |
| 0.6.124 | 6 / 2 | |
| 0.6.123 | 6 / 2 | |
| 0.6.122 | 6 / 2 | |
| 0.6.121 | 6 / 2 | |
| 0.6.120 | 6 / 2 | |
| 0.6.119 | 6 / 2 | |
| 0.6.118 | 6 / 2 | |
| 0.6.117 | 6 / 2 | |
| 0.6.116 | 6 / 2 | |
| 0.6.115 | 6 / 2 | |
| 0.6.114 | 6 / 2 | |
| 0.6.113 | 6 / 2 | |
| 0.6.112 | 6 / 2 | |
| 0.6.111 | 6 / 2 | |
| 0.6.110 | 6 / 2 | |
| 0.6.109 | 6 / 2 | |
| 0.6.108 | 6 / 2 | |
| 0.6.107 | 6 / 2 | |
| 0.6.106 | 6 / 2 | |
| 0.6.105 | 6 / 2 | |
| 0.6.104 | 6 / 2 | |
| 0.6.103 | 6 / 2 | |
| 0.6.102 | 6 / 2 | |
| 0.6.101 | 6 / 2 | |
| 0.6.100 | 6 / 2 |
v0.10.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.147
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.146
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.145
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.144
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.143
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.142
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.141
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.140
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.139
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.138
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.137
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.136
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.135
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.134
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.133
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.132
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.131
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.130
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.129
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.128
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.127
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.126
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.