@graphql-mesh/http
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 | new-deps-added | AI (publish-pattern): New deps are first-party graphql-mesh/graphql-tools sibling packages, normal monorepo split. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package convention; not indicative of risk here. | ai | |
| phantom-deps | phantom-dep:@whatwg-node/fetch | AI (phantom-deps): Genuinely used dependency; heuristic false positive from build layout. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI with SLSA provenance; consistent with org-wide migration to automated publishing. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known TypeScript runtime helper; phantom-dep false positive for compiled TS packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long gap reflects version numbering jump (v0.96 → v0.106), not true dormancy; SLSA attestation confirms legitimate CI publish. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): enisdenjo and theguild-bot are known The Guild org contributors; consistent with legitimate maintainer transition. | ai |
Versions (showing 65 of 165)
| Version | Deps | Published |
|---|---|---|
| 0.99.9 | 2 / 0 | |
| 0.99.8 | 2 / 0 | |
| 0.99.7 | 2 / 0 | |
| 0.99.6 | 2 / 0 | |
| 0.99.5 | 2 / 0 | |
| 0.99.4 | 2 / 0 | |
| 0.99.3 | 2 / 0 | |
| 0.99.2 | 2 / 0 | |
| 0.99.1 | 2 / 0 | |
| 0.99.0 | 2 / 0 | |
| 0.98.8 | 2 / 0 | |
| 0.98.7 | 2 / 0 | |
| 0.98.6 | 2 / 0 | |
| 0.98.5 | 2 / 0 | |
| 0.98.4 | 2 / 0 | |
| 0.98.3 | 2 / 0 | |
| 0.98.2 | 2 / 0 | |
| 0.98.1 | 2 / 0 | |
| 0.98.0 | 2 / 0 | |
| 0.97.7 | 2 / 0 | |
| 0.97.6 | 2 / 0 | |
| 0.97.5 | 2 / 0 | |
| 0.97.4 | 2 / 0 | |
| 0.97.3 | 2 / 0 | |
| 0.97.2 | 2 / 0 | |
| 0.97.1 | 2 / 0 | |
| 0.97.0 | 2 / 0 | |
| 0.96.14 | 2 / 0 | |
| 0.96.13 | 2 / 0 | |
| 0.96.12 | 2 / 0 | |
| 0.96.11 | 2 / 0 | |
| 0.96.10 | 2 / 0 | |
| 0.96.9 | 2 / 0 | |
| 0.96.8 | 2 / 0 | |
| 0.96.7 | 2 / 0 | |
| 0.96.6 | 2 / 0 | |
| 0.96.5 | 2 / 0 | |
| 0.96.4 | 2 / 0 | |
| 0.96.3 | 2 / 0 | |
| 0.96.2 | 2 / 0 | |
| 0.96.1 | 2 / 0 | |
| 0.96.0 | 2 / 0 | |
| 0.95.4 | 2 / 0 | |
| 0.95.3 | 2 / 0 | |
| 0.95.2 | 2 / 0 | |
| 0.95.1 | 2 / 0 | |
| 0.95.0 | 2 / 0 | |
| 0.94.5 | 2 / 0 | |
| 0.94.4 | 2 / 0 | |
| 0.94.3 | 2 / 0 | |
| 0.94.2 | 2 / 0 | |
| 0.94.1 | 2 / 0 | |
| 0.94.0 | 2 / 0 | |
| 0.93.2 | 2 / 0 | |
| 0.93.1 | 2 / 0 | |
| 0.3.29 | 3 / 0 | |
| 0.3.28 | 3 / 0 | |
| 0.3.27 | 3 / 0 | |
| 0.3.26 | 3 / 0 | |
| 0.3.25 | 7 / 0 | |
| 0.3.24 | 7 / 0 | |
| 0.3.23 | 7 / 0 | |
| 0.3.21 | 7 / 0 | |
| 0.3.20 | 7 / 0 | |
| 0.3.19 | 7 / 0 |
v0.99.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.93.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.