@graphcommerce/graphql-mesh
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:long | AI (phantom-deps): Direct runtime dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:uglify-es | AI (phantom-deps): Direct runtime dependency; stable for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 10.0.3 | 6 / 2 | |
| 10.0.2 | 6 / 2 | |
| 10.0.1 | 6 / 2 | |
| 10.0.0 | 6 / 2 |
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.