@graphql-yoga/plugin-response-cache
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 3.23.2 | 3 / 0 | |
| 3.23.0 | 3 / 0 | |
| 3.22.0 | 3 / 0 | |
| 3.21.0 | 3 / 0 | |
| 3.20.1 | 3 / 0 | |
| 3.20.0 | 3 / 0 | |
| 3.19.1 | 3 / 0 | |
| 3.19.0 | 3 / 0 | |
| 3.18.2 | 3 / 0 | |
| 3.18.1 | 3 / 0 | |
| 3.18.0 | 3 / 0 | |
| 3.17.2 | 3 / 0 | |
| 3.17.1 | 3 / 0 | |
| 3.17.0 | 3 / 0 | |
| 3.16.0 | 3 / 0 | |
| 3.15.6 | 3 / 0 | |
| 3.15.5 | 3 / 0 | |
| 3.15.4 | 3 / 0 | |
| 3.15.3 | 3 / 0 | |
| 3.15.2 | 3 / 0 | |
| 3.15.1 | 3 / 0 | |
| 3.15.0 | 2 / 0 | |
| 3.14.2 | 2 / 0 | |
| 3.14.1 | 2 / 0 | |
| 3.14.0 | 2 / 0 | |
| 3.13.1 | 2 / 0 | |
| 3.13.0 | 2 / 0 | |
| 3.12.11 | 2 / 0 | |
| 3.12.10 | 2 / 0 | |
| 3.12.9 | 2 / 0 | |
| 3.12.8 | 2 / 0 | |
| 3.12.7 | 2 / 0 | |
| 3.12.6 | 2 / 0 | |
| 3.12.5 | 2 / 0 | |
| 3.12.4 | 2 / 0 | |
| 3.12.3 | 1 / 0 | |
| 3.12.2 | 1 / 0 | |
| 3.12.1 | 1 / 0 | |
| 3.12.0 | 1 / 0 | |
| 3.11.0 | 1 / 0 | |
| 3.10.0 | 1 / 0 | |
| 3.9.0 | 1 / 0 | |
| 3.8.3 | 1 / 0 | |
| 3.8.2 | 1 / 0 | |
| 3.8.1 | 1 / 0 | |
| 3.8.0 | 1 / 0 | |
| 3.7.0 | 1 / 0 | |
| 3.6.0 | 1 / 0 |
v3.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.