@launchpad-ui/button
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:classix | AI (phantom-deps): Bundled build artifact; declared dep not directly imported in source is expected for this package. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/icons | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@launchpad-ui/tokens | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Declared dep used in build config; stable false positive for this package. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 0.15.17 | 4 / 2 | |
| 0.15.16 | 4 / 2 | |
| 0.15.15 | 4 / 2 | |
| 0.15.14 | 4 / 2 | |
| 0.15.13 | 4 / 2 | |
| 0.15.12 | 4 / 2 | |
| 0.15.11 | 4 / 2 | |
| 0.15.10 | 4 / 2 | |
| 0.15.9 | 4 / 2 | |
| 0.15.8 | 4 / 2 | |
| 0.15.7 | 4 / 2 | |
| 0.15.6 | 4 / 2 | |
| 0.15.5 | 4 / 2 | |
| 0.15.4 | 4 / 2 | |
| 0.15.3 | 4 / 2 | |
| 0.15.2 | 4 / 2 | |
| 0.15.1 | 4 / 2 | |
| 0.15.0 | 4 / 2 | |
| 0.14.0 | 4 / 2 | |
| 0.13.0 | 4 / 2 | |
| 0.12.61 | 4 / 2 | |
| 0.12.60 | 4 / 2 | |
| 0.12.59 | 4 / 2 | |
| 0.12.58 | 4 / 2 | |
| 0.12.57 | 4 / 2 | |
| 0.12.56 | 4 / 2 | |
| 0.12.55 | 4 / 2 | |
| 0.12.54 | 4 / 2 | |
| 0.12.53 | 4 / 2 | |
| 0.12.52 | 4 / 2 | |
| 0.12.51 | 4 / 2 | |
| 0.12.50 | 4 / 2 | |
| 0.12.49 | 4 / 2 | |
| 0.12.48 | 4 / 2 | |
| 0.12.47 | 4 / 2 | |
| 0.12.46 | 4 / 2 | |
| 0.12.45 | 4 / 2 | |
| 0.12.44 | 4 / 2 | |
| 0.12.43 | 4 / 2 | |
| 0.12.42 | 4 / 2 | |
| 0.12.41 | 4 / 2 | |
| 0.12.40 | 4 / 2 | |
| 0.12.39 | 4 / 2 | |
| 0.12.38 | 4 / 2 | |
| 0.12.37 | 4 / 2 | |
| 0.12.36 | 4 / 2 | |
| 0.12.35 | 4 / 2 | |
| 0.12.34 | 4 / 2 | |
| 0.12.33 | 4 / 2 | |
| 0.12.32 | 4 / 2 | |
| 0.12.31 | 4 / 2 | |
| 0.12.30 | 4 / 2 | |
| 0.12.29 | 4 / 2 | |
| 0.12.28 | 4 / 2 | |
| 0.12.27 | 4 / 2 | |
| 0.12.26 | 4 / 2 | |
| 0.12.25 | 4 / 2 | |
| 0.12.24 | 4 / 2 | |
| 0.12.23 | 4 / 2 | |
| 0.12.22 | 4 / 2 | |
| 0.12.21 | 4 / 2 | |
| 0.12.20 | 4 / 2 | |
| 0.12.19 | 4 / 2 | |
| 0.12.18 | 4 / 2 | |
| 0.12.17 | 4 / 2 | |
| 0.12.16 | 4 / 2 | |
| 0.12.15 | 4 / 2 | |
| 0.12.14 | 4 / 2 | |
| 0.12.13 | 4 / 2 | |
| 0.12.12 | 4 / 2 | |
| 0.12.11 | 4 / 2 | |
| 0.12.10 | 4 / 2 |
v0.15.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.