@segmento/waitlist-ui
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.9 | 3 / 3 | |
| 0.7.8 | 3 / 3 | |
| 0.7.7 | 3 / 3 | |
| 0.7.4 | 3 / 3 | |
| 0.7.3 | 3 / 3 | |
| 0.7.2 | 3 / 3 | |
| 0.7.1 | 3 / 3 | |
| 0.7.0 | 3 / 3 | |
| 0.6.0 | 3 / 3 | |
| 0.5.0 | 2 / 3 |
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.