@graphql-tools/batch-execute
A set of utils for faster development of GraphQL tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 51 of 259)
| Version | Deps | Published |
|---|---|---|
| 10.0.8 | 4 / 2 | |
| 10.0.7 | 4 / 2 | |
| 10.0.6 | 4 / 2 | |
| 10.0.5 | 4 / 2 | |
| 10.0.4 | 4 / 2 | |
| 10.0.3 | 4 / 2 | |
| 10.0.2 | 4 / 2 | |
| 10.0.1 | 4 / 2 | |
| 10.0.0 | 4 / 2 | |
| 9.0.19 | 4 / 2 | |
| 9.0.18 | 4 / 2 | |
| 9.0.17 | 4 / 2 | |
| 9.0.16 | 4 / 2 | |
| 9.0.15 | 4 / 2 | |
| 9.0.14 | 4 / 2 | |
| 9.0.13 | 4 / 2 | |
| 9.0.12 | 3 / 2 | |
| 9.0.11 | 3 / 2 | |
| 9.0.10 | 3 / 2 | |
| 9.0.9 | 3 / 2 | |
| 9.0.8 | 3 / 2 | |
| 9.0.7 | 3 / 2 | |
| 9.0.6 | 4 / 0 | |
| 9.0.5 | 4 / 0 | |
| 9.0.4 | 4 / 0 | |
| 9.0.3 | 4 / 0 | |
| 9.0.2 | 4 / 0 | |
| 9.0.1 | 4 / 0 | |
| 9.0.0 | 4 / 0 | |
| 8.5.22 | 4 / 0 | |
| 8.5.21 | 4 / 0 | |
| 8.5.20 | 4 / 0 | |
| 8.5.19 | 4 / 0 | |
| 8.5.18 | 4 / 0 | |
| 8.5.17 | 4 / 0 | |
| 8.5.16 | 4 / 0 | |
| 8.5.15 | 4 / 0 | |
| 8.5.14 | 4 / 0 | |
| 8.5.13 | 4 / 0 | |
| 8.5.12 | 4 / 0 | |
| 8.5.11 | 4 / 0 | |
| 8.5.10 | 4 / 0 | |
| 8.5.9 | 4 / 0 | |
| 8.5.8 | 4 / 0 | |
| 8.5.7 | 4 / 0 | |
| 8.5.6 | 4 / 0 | |
| 8.5.5 | 4 / 0 | |
| 8.5.4 | 4 / 0 | |
| 8.5.3 | 4 / 0 | |
| 8.5.2 | 4 / 0 | |
| 8.5.1 | 4 / 0 |
v10.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.