@graphql-mesh/json-schema
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): graphql-mesh migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated release pipeline. | ai | |
| provenance | slsa-provenance | AI (provenance): CI/CD published with Sigstore SLSA attestation; stable supply chain signal for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql-compose | AI (phantom-deps): graphql-compose is a declared dep used transitively; stable false positive for this org scope. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/cross-helpers | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/string-interpolation | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for monorepo packages. | ai |
Versions (showing 18 of 218)
| Version | Deps | Published |
|---|---|---|
| 0.1.15 | 7 / 1 | |
| 0.1.14 | 7 / 1 | |
| 0.1.13 | 7 / 1 | |
| 0.1.12 | 7 / 1 | |
| 0.1.11 | 7 / 1 | |
| 0.1.10 | 7 / 1 | |
| 0.1.9 | 7 / 1 | |
| 0.1.8 | 7 / 1 | |
| 0.1.7 | 7 / 1 | |
| 0.1.6 | 7 / 1 | |
| 0.1.5 | 7 / 1 | |
| 0.1.4 | 7 / 0 | |
| 0.1.3 | 7 / 0 | |
| 0.1.2 | 7 / 0 | |
| 0.1.1 | 7 / 0 | |
| 0.1.0 | 7 / 0 | |
| 0.0.22 | 7 / 0 | |
| 0.0.21 | 7 / 0 |
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.