graphql-playground-middleware-express MIT 51 versions

graphql-playground-middleware-express

npm Repository Homepage

GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).

51

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

schicklingtimsuchanekjasonkuhrtacaodivyenduzhuvik

Keywords

graphqlgraphiqlplaygroundgraphcool

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within the graphcool org; both schickling and timsuchanek are listed contributors with @graph.cool emails. Change occurred in 2018.	ai	2026/04/24
license	uncommon-license:SEE LICENSE IN LICENSE	AI (license): Standard 'SEE LICENSE IN LICENSE' pointer pattern; not a risk signal.	ai	2026/04/24

Versions (showing 51 of 59)

View all versions

Version	Deps	Published
1.7.23	1 / 4	2021-11-04
1.7.22	1 / 4	2020-10-20
1.7.21	1 / 4	2020-09-15
1.7.20	1 / 4	2020-08-30
1.7.19	1 / 4	2020-08-30
1.7.18	1 / 4	2020-06-07
1.7.16	1 / 4	2020-06-07
1.7.15	1 / 4	2020-05-28
1.7.14	1 / 4	2020-04-11
1.7.13	1 / 4	2020-04-10
1.7.12	1 / 4	2019-02-23
1.7.11	1 / 4	2019-02-01
1.7.10	1 / 4	2019-01-28
1.7.9	1 / 4	2019-01-27
1.7.8	1 / 3	2018-11-23
1.7.7	1 / 3	2018-11-14
1.7.6	1 / 3	2018-10-17
1.7.5	1 / 3	2018-10-16
1.7.4	1 / 3	2018-10-16
1.7.3	1 / 3	2018-08-23
1.7.2	1 / 3	2018-07-06
1.7.1	1 / 3	2018-06-26
1.7.0	1 / 3	2018-05-31
1.6.3	1 / 3	2018-05-24
1.6.2	1 / 3	2018-05-10
1.6.1	1 / 3	2018-04-11
1.6.0	1 / 3	2018-03-29
1.5.8	1 / 3	2018-03-22
1.5.7	1 / 3	2018-02-24
1.5.6	1 / 3	2018-01-31
1.5.4	1 / 3	2018-01-22
1.5.3	1 / 3	2018-01-15
1.5.2	1 / 3	2018-01-15
1.5.0	1 / 3	2018-01-15
1.4.9	1 / 3	2018-01-13
1.4.8	1 / 3	2018-01-08
1.4.7	1 / 3	2018-01-06
1.4.6	2 / 3	2018-01-06
1.4.5	2 / 3	2018-01-06
1.4.4	2 / 3	2018-01-05
1.4.3	2 / 3	2018-01-03
1.4.2	3 / 2	2018-01-03
1.4.1	2 / 2	2018-01-03
1.4.0	2 / 2	2018-01-03
1.3.13	2 / 2	2017-12-24
1.3.12	2 / 2	2017-12-24
1.3.11	2 / 2	2017-12-24
1.3.10	2 / 2	2017-12-22
1.3.8	2 / 2	2017-12-14
1.3.7	2 / 2	2017-12-14
1.3.6	2 / 2	2017-12-04

v1.7.23

1 finding

LOW No provenance attestation provenance

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

v1.7.22

1 finding

LOW No provenance attestation provenance

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

v1.7.21

1 finding

LOW No provenance attestation provenance

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

v1.7.20

1 finding

LOW No provenance attestation provenance

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

v1.7.19

1 finding

LOW No provenance attestation provenance

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

v1.7.18

1 finding

LOW No provenance attestation provenance

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

v1.7.16

1 finding

LOW No provenance attestation provenance

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

v1.7.15

1 finding

LOW No provenance attestation provenance

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

v1.7.14

1 finding

LOW No provenance attestation provenance

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

v1.7.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: huvik → acao (on 2020-04-10) provenance

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

v1.7.12

1 finding

LOW No provenance attestation provenance

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

v1.7.11

1 finding

LOW No provenance attestation provenance

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

v1.7.10

1 finding

LOW No provenance attestation provenance

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

v1.7.9

1 finding

LOW No provenance attestation provenance

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

v1.7.8

1 finding

LOW No provenance attestation provenance

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

v1.7.7

2 findings

HIGH Publisher changed: divyenduz → huvik (on 2018-11-14) provenance

This version was published by a different npm account than previous versions on 2018-11-14. 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.

v1.7.6

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: timsuchanek → divyenduz (on 2018-10-17) provenance

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

v1.7.5

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: divyenduz → timsuchanek (on 2018-10-16) provenance

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

v1.7.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: divyenduz → timsuchanek (on 2018-10-16) provenance

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

v1.7.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: timsuchanek → divyenduz (on 2018-08-23) provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

2 findings

HIGH Publisher changed: schickling → timsuchanek (on 2018-03-29) provenance

This version was published by a different npm account than previous versions on 2018-03-29. 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.

v1.5.8

2 findings

HIGH Publisher changed: schickling → timsuchanek (on 2018-03-22) provenance

This version was published by a different npm account than previous versions on 2018-03-22. 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.

v1.5.7

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: timsuchanek → schickling (on 2018-02-24) provenance

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

v1.5.6

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.9

1 finding

LOW No provenance attestation provenance

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

v1.4.8

1 finding

LOW No provenance attestation provenance

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

v1.4.7

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: schickling → timsuchanek (on 2018-01-06) provenance

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

v1.4.6

1 finding

LOW No provenance attestation provenance

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

v1.4.5

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: timsuchanek → schickling (on 2018-01-06) provenance

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

v1.4.4

1 finding

LOW No provenance attestation provenance

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

v1.4.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: schickling → timsuchanek (on 2018-01-03) provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.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: timsuchanek → schickling (on 2018-01-03) provenance

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

v1.4.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: schickling → timsuchanek (on 2018-01-03) provenance

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

v1.3.13

1 finding

LOW No provenance attestation provenance

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

v1.3.12

1 finding

LOW No provenance attestation provenance

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

v1.3.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: timsuchanek → schickling (on 2017-12-24) provenance

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

v1.3.10

1 finding

LOW No provenance attestation provenance

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

v1.3.8

1 finding

LOW No provenance attestation provenance

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

v1.3.7

1 finding

LOW No provenance attestation provenance

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

v1.3.6

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.