@laserfiche/types-lf-ui-components
<!--Copyright (c) Laserfiche. Licensed under the MIT License. See LICENSE in the project root for license information.-->
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 21.0.1 | 0 / 0 | |
| 21.0.0 | 0 / 0 | |
| 18.0.7 | 0 / 0 | |
| 18.0.6 | 0 / 0 | |
| 18.0.5 | 0 / 0 | |
| 18.0.4 | 0 / 0 | |
| 18.0.3 | 0 / 0 | |
| 18.0.2 | 0 / 0 | |
| 18.0.1 | 0 / 0 | |
| 18.0.0 | 0 / 0 |
v21.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v21.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.