@graphql-mesh/transport-ws
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used via graphql-ws/executor-graphql-ws; bundled ESM pattern causes phantom-dep false positive. | 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-mesh/types | AI (phantom-deps): Same-org type-only dependency; phantom-dep false positive for bundled ESM. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/utils | AI (phantom-deps): Declared dep used transitively in bundled output; stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.0.20 | 10 / 3 | |
| 2.0.19 | 10 / 3 | |
| 2.0.18 | 10 / 3 | |
| 2.0.17 | 10 / 3 | |
| 2.0.16 | 10 / 3 | |
| 2.0.15 | 10 / 3 | |
| 2.0.14 | 10 / 3 | |
| 2.0.13 | 10 / 3 | |
| 2.0.12 | 10 / 3 | |
| 2.0.11 | 10 / 3 | |
| 2.0.10 | 10 / 3 | |
| 2.0.9 | 10 / 3 | |
| 2.0.8 | 10 / 3 | |
| 2.0.7 | 10 / 3 | |
| 2.0.6 | 10 / 3 | |
| 2.0.5 | 10 / 3 | |
| 2.0.4 | 10 / 3 | |
| 2.0.3 | 10 / 3 | |
| 2.0.2 | 10 / 3 | |
| 2.0.1 | 10 / 3 | |
| 2.0.0 | 10 / 3 |
v2.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.