@podman-desktop/tests-playwright
Playwright-based testing libraries for Podman Desktop and its extensions
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.28.3 | 0 / 6 | |
| 1.28.2 | 0 / 6 | |
| 1.27.2 | 0 / 6 | |
| 1.27.1 | 0 / 6 | |
| 1.26.2 | 0 / 6 | |
| 1.26.1 | 0 / 6 | |
| 1.25.1 | 0 / 6 | |
| 1.24.2 | 0 / 5 | |
| 1.24.1 | 0 / 5 | |
| 1.23.1 | 0 / 5 | |
| 1.22.1 | 0 / 5 | |
| 1.22.0 | 0 / 5 | |
| 1.21.0 | 0 / 5 | |
| 1.20.2 | 0 / 5 | |
| 1.20.1 | 0 / 5 | |
| 1.20.0 | 0 / 5 | |
| 1.19.2 | 0 / 5 | |
| 1.19.1 | 0 / 5 | |
| 1.18.1 | 0 / 5 | |
| 1.18.0 | 0 / 5 | |
| 1.17.2 | 0 / 5 | |
| 1.17.1 | 0 / 5 | |
| 1.17.0 | 0 / 5 | |
| 1.16.2 | 0 / 5 | |
| 1.16.1 | 0 / 5 | |
| 1.16.0 | 0 / 5 | |
| 1.15.0 | 0 / 5 | |
| 1.14.2 | 0 / 5 | |
| 1.14.1 | 0 / 5 | |
| 1.14.0 | 0 / 5 | |
| 1.13.3 | 0 / 5 | |
| 1.13.2 | 0 / 5 | |
| 1.12.0 | 0 / 5 | |
| 1.11.1 | 0 / 5 | |
| 1.11.0 | 0 / 5 | |
| 1.10.3 | 0 / 5 | |
| 1.10.2 | 0 / 5 | |
| 1.10.1 | 0 / 5 | |
| 1.10.0 | 0 / 5 | |
| 1.9.1 | 0 / 5 | |
| 1.9.0 | 0 / 5 |
v1.28.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.