@graphql-tools/executor-http
A set of utils for faster development of GraphQL tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 9 / 7 | |
| 3.2.1 | 9 / 7 | |
| 3.2.0 | 9 / 7 | |
| 3.1.4 | 9 / 7 | |
| 3.1.3 | 9 / 7 | |
| 3.1.2 | 9 / 7 | |
| 3.1.1 | 9 / 7 | |
| 3.1.0 | 9 / 7 | |
| 3.0.7 | 9 / 7 | |
| 3.0.6 | 9 / 7 | |
| 3.0.5 | 9 / 7 | |
| 3.0.4 | 9 / 7 | |
| 3.0.3 | 9 / 7 | |
| 3.0.2 | 9 / 7 | |
| 3.0.1 | 9 / 7 | |
| 3.0.0 | 9 / 7 | |
| 2.1.2 | 9 / 7 | |
| 2.1.1 | 9 / 7 | |
| 2.1.0 | 9 / 7 | |
| 2.0.3 | 9 / 7 | |
| 2.0.2 | 9 / 7 | |
| 2.0.1 | 9 / 7 | |
| 2.0.0 | 9 / 7 | |
| 1.3.3 | 9 / 7 | |
| 1.3.2 | 9 / 7 | |
| 1.3.1 | 8 / 7 | |
| 1.3.0 | 8 / 7 | |
| 1.2.8 | 9 / 6 | |
| 1.2.7 | 9 / 6 | |
| 1.2.6 | 9 / 6 | |
| 1.2.5 | 10 / 6 | |
| 1.2.4 | 10 / 6 | |
| 1.2.3 | 10 / 6 | |
| 1.2.2 | 9 / 6 | |
| 1.2.1 | 9 / 6 | |
| 1.2.0 | 8 / 6 | |
| 1.1.14 | 8 / 5 | |
| 1.1.13 | 8 / 5 | |
| 1.1.12 | 8 / 5 | |
| 1.1.11 | 8 / 5 | |
| 1.1.10 | 8 / 5 | |
| 1.1.9 | 7 / 0 | |
| 1.1.8 | 7 / 0 | |
| 1.1.7 | 7 / 0 | |
| 1.1.6 | 7 / 0 | |
| 1.1.5 | 7 / 0 | |
| 1.1.4 | 7 / 0 | |
| 1.1.3 | 7 / 0 | |
| 1.1.2 | 7 / 0 | |
| 1.1.1 | 7 / 0 | |
| 1.1.0 | 7 / 0 | |
| 1.0.9 | 7 / 0 | |
| 1.0.8 | 7 / 0 | |
| 1.0.7 | 7 / 0 | |
| 1.0.6 | 7 / 0 | |
| 1.0.5 | 7 / 0 | |
| 1.0.4 | 7 / 0 | |
| 1.0.3 | 7 / 0 | |
| 1.0.2 | 7 / 0 | |
| 1.0.1 | 7 / 0 | |
| 1.0.0 | 8 / 0 | |
| 0.1.10 | 8 / 0 | |
| 0.1.9 | 8 / 0 | |
| 0.1.8 | 8 / 0 | |
| 0.1.7 | 8 / 0 | |
| 0.1.6 | 8 / 0 | |
| 0.1.5 | 8 / 0 | |
| 0.1.4 | 8 / 0 | |
| 0.1.3 | 8 / 0 | |
| 0.1.2 | 8 / 0 | |
| 0.1.1 | 8 / 0 | |
| 0.1.0 | 8 / 0 | |
| 0.0.9 | 8 / 0 | |
| 0.0.8 | 8 / 0 | |
| 0.0.7 | 8 / 0 | |
| 0.0.6 | 8 / 0 | |
| 0.0.5 | 8 / 0 | |
| 0.0.4 | 8 / 0 | |
| 0.0.3 | 8 / 0 | |
| 0.0.2 | 8 / 0 | |
| 0.0.1 | 8 / 0 |
v3.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.