@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, so a manually published version cannot be tied back to a reviewed commit.
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 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.101.4 | 12 / 0 | |
| 0.101.3 | 12 / 0 | |
| 0.101.2 | 12 / 0 | |
| 0.101.1 | 12 / 0 | |
| 0.101.0 | 12 / 0 | |
| 0.100.12 | 12 / 0 | |
| 0.100.11 | 12 / 0 | |
| 0.100.10 | 12 / 0 | |
| 0.100.9 | 12 / 0 | |
| 0.100.8 | 12 / 0 | |
| 0.100.7 | 12 / 0 | |
| 0.100.6 | 12 / 0 | |
| 0.100.5 | 12 / 0 | |
| 0.100.4 | 12 / 0 | |
| 0.100.3 | 12 / 0 | |
| 0.100.2 | 12 / 0 | |
| 0.100.1 | 12 / 0 | |
| 0.97.4 | 12 / 0 |
v0.101.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.101.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.101.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.