@argos-ci/gitlab
GitLab utilities for visual testing with Argos.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 0.7.14 | 3 / 1 | |
| 0.7.13 | 3 / 1 | |
| 0.7.12 | 3 / 1 | |
| 0.7.8 | 3 / 1 | |
| 0.7.7 | 3 / 1 | |
| 0.7.6 | 3 / 1 | |
| 0.7.5 | 3 / 1 | |
| 0.7.4 | 3 / 1 | |
| 0.7.3 | 3 / 1 | |
| 0.7.2 | 3 / 1 | |
| 0.7.1 | 3 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.1 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.4 | 3 / 1 | |
| 0.4.3 | 3 / 1 | |
| 0.4.2 | 3 / 1 | |
| 0.4.1 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.4 | 3 / 1 | |
| 0.3.3 | 3 / 1 | |
| 0.3.2 | 3 / 1 | |
| 0.3.1 | 3 / 1 | |
| 0.3.0 | 3 / 1 | |
| 0.2.5 | 3 / 1 | |
| 0.2.4 | 3 / 1 | |
| 0.2.3 | 3 / 1 | |
| 0.2.2 | 3 / 1 | |
| 0.2.1 | 3 / 1 | |
| 0.2.0 | 3 / 1 | |
| 0.1.10 | 3 / 1 | |
| 0.1.9 | 3 / 1 | |
| 0.1.8 | 3 / 1 | |
| 0.1.7 | 3 / 1 | |
| 0.1.6 | 3 / 1 | |
| 0.1.5 | 3 / 1 | |
| 0.1.4 | 3 / 1 | |
| 0.1.3 | 3 / 1 |
v0.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.