← Home

@stratasync/transport-graphql

npm Repository Homepage

GraphQL transport adapter for sync communication and mutations.

5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mblode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@stratasync/client AI (dependencies): @stratasync/client is a sibling package in the same monorepo/org; the wildcard constraint is an internal monorepo pattern, not a supply chain risk. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); no other risk signals elevate this to a concern for this package. ai

Versions (showing 5 of 5)

Version Deps Published
0.2.4 3 / 2
0.2.3 3 / 2
0.2.2 3 / 6
0.2.1 3 / 6
0.2.0 3 / 6

v0.2.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.