@graphql-tools/json-file-loader
A set of utils for faster development of GraphQL tools
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 337)
| Version | Deps | Published |
|---|---|---|
| 8.0.28 | 4 / 0 | |
| 8.0.27 | 4 / 0 | |
| 8.0.26 | 4 / 0 | |
| 8.0.25 | 4 / 0 | |
| 8.0.24 | 4 / 0 | |
| 8.0.23 | 4 / 0 | |
| 8.0.22 | 4 / 0 | |
| 8.0.21 | 4 / 0 | |
| 8.0.20 | 4 / 0 | |
| 8.0.19 | 4 / 0 | |
| 8.0.18 | 4 / 0 | |
| 8.0.17 | 4 / 0 | |
| 8.0.16 | 4 / 0 | |
| 8.0.15 | 4 / 0 | |
| 8.0.14 | 4 / 0 | |
| 8.0.13 | 4 / 0 | |
| 8.0.12 | 4 / 0 | |
| 8.0.11 | 4 / 0 | |
| 8.0.10 | 4 / 0 | |
| 8.0.9 | 4 / 0 | |
| 8.0.8 | 4 / 0 | |
| 8.0.7 | 4 / 0 | |
| 8.0.6 | 4 / 0 | |
| 8.0.5 | 4 / 0 | |
| 8.0.4 | 4 / 0 | |
| 8.0.3 | 4 / 0 | |
| 8.0.2 | 4 / 0 | |
| 8.0.1 | 4 / 0 | |
| 8.0.0 | 4 / 0 | |
| 7.4.18 | 4 / 0 | |
| 7.4.17 | 4 / 0 | |
| 7.4.16 | 4 / 0 | |
| 7.4.15 | 4 / 0 | |
| 7.4.14 | 4 / 0 | |
| 7.4.13 | 4 / 0 | |
| 7.4.12 | 4 / 0 | |
| 7.4.11 | 4 / 0 | |
| 7.4.10 | 4 / 0 | |
| 7.4.9 | 4 / 0 | |
| 7.4.8 | 4 / 0 | |
| 7.4.7 | 4 / 0 | |
| 7.4.6 | 4 / 0 | |
| 7.4.5 | 4 / 0 | |
| 7.4.4 | 4 / 0 | |
| 7.4.3 | 4 / 0 | |
| 7.4.2 | 4 / 0 | |
| 7.4.1 | 4 / 0 | |
| 7.4.0 | 4 / 0 | |
| 7.3.16 | 4 / 0 | |
| 7.3.15 | 4 / 0 | |
| 7.3.14 | 4 / 0 | |
| 7.3.13 | 4 / 0 | |
| 7.3.12 | 4 / 0 | |
| 7.3.11 | 4 / 0 | |
| 7.3.10 | 4 / 0 | |
| 7.3.9 | 4 / 0 | |
| 7.3.8 | 4 / 0 | |
| 7.3.7 | 4 / 0 | |
| 7.3.6 | 4 / 0 | |
| 7.3.5 | 4 / 0 | |
| 7.3.4 | 4 / 0 | |
| 7.3.3 | 4 / 0 | |
| 7.3.2 | 4 / 0 | |
| 7.3.1 | 4 / 0 | |
| 7.3.0 | 4 / 0 | |
| 7.2.0 | 4 / 0 | |
| 7.1.3 | 4 / 0 | |
| 7.1.2 | 4 / 0 | |
| 7.1.1 | 4 / 0 | |
| 7.1.0 | 4 / 0 | |
| 7.0.2 | 2 / 0 | |
| 7.0.1 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.2.6 | 2 / 0 | |
| 6.2.5 | 3 / 0 | |
| 6.2.4 | 3 / 0 | |
| 6.2.3 | 3 / 0 | |
| 6.2.2 | 3 / 0 | |
| 6.2.1 | 3 / 0 | |
| 6.2.0 | 3 / 0 | |
| 6.1.0 | 3 / 0 | |
| 6.0.18 | 3 / 0 | |
| 6.0.17 | 3 / 0 | |
| 6.0.16 | 3 / 0 | |
| 6.0.15 | 3 / 0 | |
| 6.0.14 | 3 / 0 | |
| 6.0.13 | 3 / 0 | |
| 6.0.12 | 3 / 0 | |
| 6.0.11 | 3 / 0 | |
| 6.0.10 | 3 / 0 | |
| 6.0.9 | 3 / 0 | |
| 6.0.8 | 3 / 0 | |
| 6.0.7 | 3 / 0 | |
| 6.0.6 | 3 / 0 | |
| 6.0.5 | 3 / 0 | |
| 6.0.4 | 3 / 0 | |
| 6.0.3 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.1 | 3 / 0 | |
| 6.0.0 | 3 / 0 |
v8.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.7
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.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.13
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.
v7.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.