@launchpad-ui/menu
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 CSS token package; indirect usage via CSS imports is expected for this component library. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.16.17 | 9 / 2 | |
| 0.16.16 | 9 / 2 | |
| 0.16.15 | 9 / 2 | |
| 0.16.14 | 10 / 2 | |
| 0.16.13 | 10 / 2 | |
| 0.16.11 | 10 / 2 | |
| 0.16.10 | 10 / 2 | |
| 0.16.9 | 10 / 2 | |
| 0.16.8 | 10 / 2 | |
| 0.16.7 | 10 / 2 | |
| 0.16.6 | 10 / 2 | |
| 0.16.5 | 10 / 2 | |
| 0.16.4 | 10 / 2 | |
| 0.16.3 | 10 / 2 | |
| 0.16.2 | 10 / 2 | |
| 0.16.1 | 10 / 2 | |
| 0.16.0 | 10 / 2 | |
| 0.15.0 | 10 / 2 | |
| 0.14.0 | 10 / 2 | |
| 0.13.69 | 10 / 2 | |
| 0.13.68 | 10 / 2 | |
| 0.13.67 | 10 / 2 | |
| 0.13.66 | 10 / 2 | |
| 0.13.65 | 10 / 2 | |
| 0.13.64 | 10 / 2 | |
| 0.13.63 | 10 / 2 | |
| 0.13.62 | 10 / 2 | |
| 0.13.61 | 10 / 2 | |
| 0.13.60 | 10 / 2 | |
| 0.13.59 | 10 / 2 | |
| 0.13.58 | 10 / 2 | |
| 0.13.57 | 10 / 2 | |
| 0.13.56 | 10 / 2 | |
| 0.13.55 | 10 / 2 | |
| 0.13.54 | 10 / 2 | |
| 0.13.53 | 10 / 2 | |
| 0.13.52 | 10 / 2 | |
| 0.13.51 | 10 / 2 | |
| 0.13.50 | 10 / 2 | |
| 0.13.49 | 10 / 2 | |
| 0.13.48 | 10 / 2 | |
| 0.13.47 | 10 / 2 | |
| 0.13.46 | 10 / 2 | |
| 0.13.45 | 10 / 2 | |
| 0.13.44 | 10 / 2 | |
| 0.13.43 | 10 / 2 | |
| 0.13.42 | 10 / 2 | |
| 0.13.41 | 10 / 2 | |
| 0.13.40 | 10 / 2 | |
| 0.13.39 | 10 / 2 | |
| 0.13.38 | 10 / 2 | |
| 0.13.37 | 10 / 2 | |
| 0.13.36 | 10 / 2 | |
| 0.13.35 | 10 / 2 | |
| 0.13.34 | 10 / 2 | |
| 0.13.33 | 10 / 2 | |
| 0.13.32 | 10 / 2 | |
| 0.13.31 | 10 / 2 | |
| 0.13.30 | 10 / 2 | |
| 0.13.29 | 10 / 2 | |
| 0.13.28 | 10 / 2 | |
| 0.13.27 | 10 / 2 | |
| 0.13.26 | 10 / 2 | |
| 0.13.25 | 10 / 2 | |
| 0.13.24 | 10 / 2 | |
| 0.13.23 | 10 / 2 | |
| 0.13.22 | 10 / 2 | |
| 0.13.21 | 10 / 2 | |
| 0.13.20 | 10 / 2 | |
| 0.13.19 | 10 / 2 | |
| 0.13.18 | 10 / 2 | |
| 0.13.17 | 10 / 2 | |
| 0.13.16 | 10 / 2 | |
| 0.13.15 | 10 / 2 | |
| 0.13.14 | 10 / 2 | |
| 0.13.13 | 10 / 2 | |
| 0.13.12 | 10 / 2 | |
| 0.13.11 | 10 / 2 |
v0.16.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.