@graphql-tools/executor-graphql-ws
A set of utils for faster development of GraphQL tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 3.1.5 | 7 / 3 | |
| 3.1.4 | 7 / 3 | |
| 3.1.3 | 7 / 3 | |
| 3.1.2 | 7 / 3 | |
| 3.1.1 | 7 / 3 | |
| 3.1.0 | 7 / 3 | |
| 3.0.1 | 7 / 3 | |
| 3.0.0 | 7 / 3 | |
| 2.0.7 | 7 / 3 | |
| 2.0.6 | 7 / 3 | |
| 2.0.5 | 7 / 3 | |
| 2.0.4 | 7 / 3 | |
| 2.0.3 | 7 / 3 | |
| 2.0.2 | 7 / 3 | |
| 2.0.1 | 7 / 3 | |
| 2.0.0 | 7 / 3 | |
| 1.3.7 | 7 / 3 | |
| 1.3.6 | 6 / 3 | |
| 1.3.5 | 6 / 3 | |
| 1.3.4 | 6 / 3 | |
| 1.3.3 | 6 / 3 | |
| 1.3.2 | 6 / 0 | |
| 1.3.1 | 6 / 0 | |
| 1.3.0 | 6 / 0 | |
| 1.2.1 | 6 / 0 | |
| 1.2.0 | 6 / 0 | |
| 1.1.2 | 6 / 0 | |
| 1.1.1 | 6 / 0 | |
| 1.1.0 | 6 / 0 | |
| 1.0.2 | 6 / 0 | |
| 1.0.1 | 7 / 0 | |
| 1.0.0 | 7 / 0 | |
| 0.0.14 | 7 / 0 | |
| 0.0.13 | 7 / 0 | |
| 0.0.12 | 7 / 0 | |
| 0.0.11 | 7 / 0 | |
| 0.0.10 | 7 / 0 | |
| 0.0.9 | 7 / 0 | |
| 0.0.8 | 7 / 0 | |
| 0.0.7 | 7 / 0 | |
| 0.0.6 | 7 / 0 | |
| 0.0.5 | 7 / 0 | |
| 0.0.4 | 7 / 0 | |
| 0.0.3 | 7 / 0 | |
| 0.0.2 | 7 / 0 | |
| 0.0.1 | 7 / 0 |
v3.1.5
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.