@launchpad-ui/popover
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 7 / 2 | |
| 0.14.4 | 7 / 2 | |
| 0.14.3 | 7 / 2 | |
| 0.14.2 | 7 / 2 | |
| 0.14.1 | 7 / 2 | |
| 0.14.0 | 7 / 2 | |
| 0.13.0 | 7 / 2 | |
| 0.12.0 | 7 / 2 | |
| 0.11.48 | 7 / 2 | |
| 0.11.47 | 7 / 2 | |
| 0.11.46 | 7 / 2 | |
| 0.11.45 | 7 / 2 | |
| 0.11.44 | 7 / 2 | |
| 0.11.43 | 7 / 2 | |
| 0.11.42 | 7 / 2 | |
| 0.11.41 | 7 / 2 | |
| 0.11.40 | 7 / 2 | |
| 0.11.39 | 7 / 2 | |
| 0.11.38 | 7 / 2 | |
| 0.11.37 | 7 / 2 | |
| 0.11.36 | 7 / 2 | |
| 0.11.35 | 7 / 2 | |
| 0.11.34 | 7 / 2 | |
| 0.11.33 | 7 / 2 | |
| 0.11.32 | 7 / 2 | |
| 0.11.31 | 7 / 2 | |
| 0.11.30 | 7 / 2 | |
| 0.11.29 | 7 / 2 | |
| 0.11.28 | 7 / 2 | |
| 0.11.27 | 7 / 2 | |
| 0.11.26 | 7 / 2 | |
| 0.11.25 | 7 / 2 | |
| 0.11.24 | 7 / 2 | |
| 0.11.23 | 7 / 2 | |
| 0.11.22 | 7 / 2 | |
| 0.11.21 | 7 / 2 |
v0.14.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.