@launchpad-ui/progress
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.5.57 | 2 / 2 | |
| 0.5.56 | 2 / 2 | |
| 0.5.55 | 2 / 2 | |
| 0.5.54 | 2 / 2 | |
| 0.5.53 | 2 / 2 | |
| 0.5.52 | 2 / 2 | |
| 0.5.51 | 2 / 2 | |
| 0.5.50 | 2 / 2 | |
| 0.5.49 | 2 / 2 | |
| 0.5.48 | 2 / 2 | |
| 0.5.47 | 2 / 2 | |
| 0.5.46 | 2 / 2 |
v0.5.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.