← Home

@cedarjs/graphql-server

npm Repository Homepage
15
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tobbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Only ~12% of npm packages have provenance; not a disqualifier for established packages. ai
phantom-deps phantom-dep:@babel/runtime-corejs3 AI (phantom-deps): Framework-scoped package loaded by Babel convention; stable for this package. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): Implicit runtime dependency; stable pattern for Babel-transpiled packages. ai
dependencies unvetted-dep:@envelop/filter-operation-type AI (dependencies): Standard GraphQL envelop plugin; stable ecosystem package used across graphql-server versions. ai
dependencies unvetted-dep:@envelop/depth-limit AI (dependencies): Standard GraphQL envelop plugin; stable ecosystem package used across graphql-server versions. ai
dependencies unvetted-dep:@escape.tech/graphql-armor AI (dependencies): Well-known GraphQL security library; expected dependency for this package. ai
bogus-package bogus-package AI (bogus-package): Established framework package; sparse README/keywords are a style choice, not spam. ai
phantom-deps phantom-dep:@envelop/depth-limit AI (phantom-deps): Declared as a runtime dep; phantom-dep heuristic fires on config-only references, not a real concern here. ai

Versions (showing 15 of 15)

Version Deps Published
4.2.0 20 / 17
4.1.0 20 / 17
4.0.0 19 / 17
3.1.1 19 / 17
3.1.0 19 / 17
3.0.0 19 / 17
2.7.0 21 / 17
2.5.1 21 / 17
2.2.1 21 / 17
2.1.1 21 / 18
2.1.0 21 / 18
2.0.2 21 / 18
2.0.1 21 / 18
2.0.0 21 / 18
1.1.0 21 / 18

v4.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.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.

v3.1.1

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.

v3.1.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.

v3.0.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.

v2.7.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.

v2.5.1

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.

v2.2.1

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.

v2.1.1

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.

v2.1.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.

v2.0.2

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.

v2.0.1

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.

v2.0.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.

v1.1.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.