graphql-skip-limit MIT 50 versions

graphql-skip-limit

npm Repository Homepage

A library to help construct a graphql-js server supporting skip/relay style pagination. Built for Gatsby but perhaps useful elsewhere.

50

Versions

MIT

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

ascorbicblainekastendschaufkfreiksenetjamojohnokuvoskylemathewslaurieontechlekoartsm-allansonmadalynrosemonastic.panicmoocarpiehsidharthachatterjeesmthomastylerbarnesvladarwardpeet

Keywords

gatsbygraphql

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from freiksenet to sidharthachatterjee reflects a legitimate Gatsby team transition in 2020; sidharthachatterjee is a known Gatsby core contributor with strong track record.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): laurieontech is a known Gatsby team member; addition reflects legitimate team growth, not a takeover.	ai	2026/04/23
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): @babel/runtime is a Babel transform helper injected by convention in Gatsby packages; not a real phantom dependency risk.	ai	2026/04/23

Versions (showing 50 of 50)

Version	Deps	Published
2.3.1	1 / 5	2020-05-05
2.3.0	1 / 5	2020-04-27
2.2.3	1 / 5	2020-04-24
2.2.2	1 / 5	2020-04-16
2.2.1	1 / 5	2020-03-23
2.2.0	1 / 5	2020-03-20
2.1.27	1 / 5	2020-03-16
2.1.26	1 / 5	2020-03-06
2.1.25	1 / 5	2020-02-01
2.1.24	1 / 5	2020-01-09
2.1.23	1 / 5	2019-12-10
2.1.21	1 / 5	2019-11-26
2.1.20	1 / 5	2019-11-15
2.1.19	1 / 5	2019-11-10
2.1.18	1 / 5	2019-10-14
2.1.17	1 / 5	2019-10-14
2.1.16	1 / 5	2019-10-09
2.1.15	1 / 5	2019-09-26
2.1.13	1 / 5	2019-09-25
2.1.12	1 / 5	2019-09-20
2.1.11	1 / 5	2019-09-20
2.1.10	1 / 5	2019-09-16
2.1.9	1 / 5	2019-09-09
2.1.8	1 / 5	2019-09-01
2.1.7	1 / 5	2019-08-29
2.1.6	1 / 5	2019-08-24
2.1.5	1 / 5	2019-08-23
2.1.4	1 / 5	2019-08-23
2.1.3	1 / 5	2019-08-20
2.1.2	1 / 5	2019-07-12
2.1.1	1 / 5	2019-07-11
2.1.0	1 / 5	2019-06-20
2.0.6	1 / 5	2019-03-11
2.0.5	1 / 5	2019-02-01
2.0.4	1 / 5	2018-12-17
2.0.3	1 / 5	2018-12-07
2.0.2	1 / 5	2018-11-29
2.0.1	1 / 5	2018-10-29
2.0.0	1 / 4	2018-09-17
1.0.11	2 / 2	2018-02-28
1.0.10	2 / 2	2018-02-13
1.0.9	2 / 3	2017-12-20
1.0.8	2 / 3	2017-11-29
1.0.7	2 / 3	2017-11-01
1.0.6	1 / 3	2017-10-02
1.0.5	1 / 3	2017-08-31
1.0.4	1 / 2	2017-08-30
1.0.3	1 / 2	2017-08-25
1.0.2	1 / 2	2017-08-19
1.0.1	0 / 2	2017-07-06

v2.3.1

2 findings

HIGH Publisher changed: freiksenet → sidharthachatterjee (on 2020-05-05) provenance

This version was published by a different npm account than previous versions on 2020-05-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: vladar → freiksenet (on 2020-04-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-27. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kylemathews → vladar (on 2020-04-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-24. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: freiksenet → kylemathews (on 2020-04-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-16. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: freiksenet → pieh (on 2020-03-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-23. This could indicate a legitimate maintainer transition or an account compromise.

v2.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → freiksenet (on 2020-03-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.27

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: blainekasten → wardpeet (on 2020-03-16) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-16. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.26

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sidharthachatterjee → blainekasten (on 2020-03-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-06. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.25

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: tylerbarnes → sidharthachatterjee (on 2020-02-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-02-01. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.24

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: freiksenet → tylerbarnes (on 2020-01-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-09. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.23

1 finding

LOW No provenance attestation provenance

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

v2.1.21

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → freiksenet (on 2019-11-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-26. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.20

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sidharthachatterjee → wardpeet (on 2019-11-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-15. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.19

1 finding

LOW No provenance attestation provenance

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

v2.1.18

1 finding

LOW No provenance attestation provenance

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

v2.1.17

1 finding

LOW No provenance attestation provenance

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

v2.1.16

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → sidharthachatterjee (on 2019-10-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-09. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.15

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: pieh → wardpeet (on 2019-09-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-26. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.13

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dschau → pieh (on 2019-09-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-25. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.12

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: pieh → dschau (on 2019-09-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.11

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → pieh (on 2019-09-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.10

1 finding

LOW No provenance attestation provenance

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

v2.1.9

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sidharthachatterjee → wardpeet (on 2019-09-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-09. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.8

1 finding

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → sidharthachatterjee (on 2019-08-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-23. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → sidharthachatterjee (on 2019-08-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-08-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: wardpeet → sidharthachatterjee (on 2019-07-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-12. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dschau → wardpeet (on 2019-07-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-07-11. This could indicate a legitimate maintainer transition or an account compromise.

v2.1.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: pieh → dschau (on 2019-06-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-20. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dschau → pieh (on 2018-12-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-17. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: pieh → dschau (on 2018-12-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-12-07. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dschau → pieh (on 2018-11-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-29. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: kylemathews → dschau (on 2018-10-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-29. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

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