@graphql-tools/graphql-tag-pluck
Pluck graphql-tag template literals
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 51 of 121)
| Version | Deps | Published |
|---|---|---|
| 8.3.33 | 7 / 0 | |
| 8.3.32 | 7 / 0 | |
| 8.3.31 | 7 / 0 | |
| 8.3.30 | 7 / 0 | |
| 8.3.29 | 7 / 0 | |
| 8.3.28 | 7 / 0 | |
| 8.3.27 | 7 / 0 | |
| 8.3.26 | 7 / 0 | |
| 8.3.25 | 7 / 0 | |
| 8.3.24 | 7 / 0 | |
| 8.3.23 | 7 / 0 | |
| 8.3.22 | 7 / 0 | |
| 8.3.21 | 7 / 0 | |
| 8.3.20 | 7 / 0 | |
| 8.3.19 | 7 / 0 | |
| 8.3.18 | 7 / 0 | |
| 8.3.17 | 7 / 0 | |
| 8.3.16 | 7 / 0 | |
| 8.3.15 | 7 / 0 | |
| 8.3.14 | 7 / 0 | |
| 8.3.13 | 7 / 0 | |
| 8.3.12 | 7 / 0 | |
| 8.3.11 | 7 / 0 | |
| 8.3.10 | 7 / 0 | |
| 8.3.9 | 7 / 0 | |
| 8.3.8 | 7 / 0 | |
| 8.3.7 | 7 / 0 | |
| 8.3.6 | 7 / 0 | |
| 8.3.5 | 7 / 0 | |
| 8.3.4 | 7 / 0 | |
| 8.3.3 | 7 / 0 | |
| 8.3.2 | 7 / 0 | |
| 8.3.1 | 7 / 0 | |
| 8.1.0 | 7 / 0 | |
| 8.0.2 | 7 / 0 | |
| 8.0.1 | 6 / 0 | |
| 8.0.0 | 6 / 0 | |
| 7.5.2 | 6 / 0 | |
| 7.5.1 | 6 / 0 | |
| 7.5.0 | 6 / 0 | |
| 7.4.6 | 6 / 0 | |
| 7.4.5 | 6 / 0 | |
| 7.4.4 | 6 / 0 | |
| 7.4.3 | 6 / 0 | |
| 7.4.2 | 6 / 0 | |
| 7.4.1 | 6 / 0 | |
| 7.4.0 | 6 / 0 | |
| 7.3.12 | 5 / 0 | |
| 7.3.11 | 5 / 0 | |
| 7.3.10 | 5 / 0 | |
| 7.3.9 | 5 / 0 |
v8.3.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.3.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.