@graphql-mesh/config
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long gap reflects monorepo release cadence, not account takeover; SLSA provenance confirms CI origin. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from ardatan to GitHub Actions CI/CD with SLSA provenance; consistent with org-level automation migration. | ai | |
| phantom-deps | phantom-dep:graphql-yoga | AI (phantom-deps): graphql-yoga is a direct dep used in config resolution; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/merger-bare | AI (phantom-deps): Same-org monorepo dep; declared as default merger, not directly imported in config code. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/merger-stitching | AI (phantom-deps): Same-org monorepo dep; declared as default merger, not directly imported in config code. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/cache-localforage | AI (phantom-deps): Same-org monorepo dep; declared as default cache, not directly imported in config code. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.108.44 | 20 / 0 | |
| 0.108.43 | 20 / 0 | |
| 0.108.42 | 20 / 0 | |
| 0.108.41 | 20 / 0 | |
| 0.108.40 | 20 / 0 | |
| 0.108.39 | 20 / 0 | |
| 0.108.38 | 20 / 0 | |
| 0.108.37 | 20 / 0 | |
| 0.108.36 | 20 / 0 | |
| 0.108.35 | 20 / 0 | |
| 0.108.34 | 20 / 0 | |
| 0.108.33 | 20 / 0 | |
| 0.108.32 | 20 / 0 | |
| 0.108.31 | 20 / 0 | |
| 0.108.30 | 20 / 0 | |
| 0.108.29 | 20 / 0 | |
| 0.108.28 | 20 / 0 | |
| 0.108.27 | 20 / 0 | |
| 0.108.26 | 20 / 0 | |
| 0.108.25 | 20 / 0 | |
| 0.108.24 | 20 / 0 | |
| 0.108.23 | 20 / 0 | |
| 0.108.22 | 20 / 0 | |
| 0.108.21 | 20 / 0 | |
| 0.108.20 | 20 / 0 | |
| 0.108.19 | 20 / 0 | |
| 0.108.18 | 20 / 0 | |
| 0.108.17 | 20 / 0 | |
| 0.108.16 | 20 / 0 | |
| 0.108.15 | 20 / 0 | |
| 0.108.14 | 20 / 0 | |
| 0.108.13 | 20 / 0 | |
| 0.108.12 | 20 / 0 | |
| 0.108.11 | 20 / 0 | |
| 0.108.10 | 20 / 0 | |
| 0.108.9 | 20 / 0 | |
| 0.108.8 | 20 / 0 | |
| 0.108.7 | 20 / 0 | |
| 0.108.6 | 20 / 0 | |
| 0.108.5 | 20 / 0 | |
| 0.97.4 | 12 / 0 |
v0.108.38
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.37
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.36
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.35
2 findingsThis version was published by a different npm account than previous versions on 2026-03-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.34
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.33
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.32
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.108.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.