graphql-playground-middleware-lambda MIT 45 versions

graphql-playground-middleware-lambda

npm Repository Homepage

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

45

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

graphqlgraphiqlplaygroundgraphcoollambada

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 divyenduz to huvik occurred in Nov 2018 — over 6 years ago. huvik has a strong track record (515 approved packages) and has maintained this package stably across many versions since then.	ai	2026/04/24

Versions (showing 45 of 45)

Version	Deps	Published
1.7.24	1 / 4	2021-11-04
1.7.23	1 / 4	2020-10-20
1.7.22	1 / 4	2020-09-15
1.7.21	1 / 4	2020-08-30
1.7.20	1 / 4	2020-08-30
1.7.19	1 / 4	2020-06-07
1.7.17	1 / 4	2020-06-07
1.7.16	1 / 4	2020-05-28
1.7.15	1 / 4	2020-04-11
1.7.14	1 / 4	2020-04-10
1.7.13	1 / 4	2019-02-23
1.7.12	1 / 4	2019-02-01
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.1	1 / 3	2018-05-24
1.6.0	1 / 3	2018-05-18
1.5.1	1 / 3	2018-04-11
1.5.0	1 / 3	2018-03-29
1.4.4	1 / 3	2018-03-22
1.4.3	1 / 3	2018-02-24
1.4.2	1 / 3	2018-01-31
1.4.1	1 / 3	2018-01-22
1.4.0	1 / 3	2018-01-15
1.3.10	1 / 3	2018-01-13
1.3.9	1 / 3	2018-01-06
1.3.8	1 / 3	2018-01-06
1.3.7	2 / 3	2018-01-05
1.3.6	2 / 2	2017-12-04
1.3.5	2 / 2	2017-12-04
1.3.1	1 / 2	2017-12-01
1.3.0	1 / 2	2017-12-01
1.2.0	0 / 2	2017-11-24
1.1.4	0 / 2	2017-11-15
1.1.3	0 / 2	2017-11-15
1.1.2	0 / 2	2017-11-07

v1.7.24

1 finding

LOW No provenance attestation provenance

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

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

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

2 findings

HIGH Publisher changed: timsuchanek → acao (on 2020-04-10) provenance

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.

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

HIGH Publisher changed: timsuchanek → huvik (on 2019-02-23) provenance

This version was published by a different npm account than previous versions on 2019-02-23. 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.12

2 findings

HIGH Publisher changed: timsuchanek → huvik (on 2019-02-01) provenance

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

2 findings

HIGH Publisher changed: timsuchanek → huvik (on 2019-02-01) provenance

This version was published by a different npm account than previous versions on 2019-02-01. 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.10

2 findings

HIGH Publisher changed: timsuchanek → huvik (on 2019-01-28) provenance

This version was published by a different npm account than previous versions on 2019-01-28. 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.9

2 findings

HIGH Publisher changed: timsuchanek → huvik (on 2019-01-27) provenance

This version was published by a different npm account than previous versions on 2019-01-27. 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.8

2 findings

HIGH Publisher changed: timsuchanek → huvik (on 2018-11-23) provenance

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

HIGH Publisher changed: timsuchanek → divyenduz (on 2018-10-17) provenance

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.

LOW No provenance attestation provenance

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

v1.7.5

1 finding

LOW No provenance attestation provenance

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

v1.7.4

2 findings

HIGH Publisher changed: divyenduz → timsuchanek (on 2018-10-16) provenance

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.

LOW No provenance attestation provenance

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

v1.7.3

2 findings

HIGH Publisher changed: timsuchanek → divyenduz (on 2018-08-23) provenance

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.

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.5.1

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

HIGH Publisher changed: timsuchanek → schickling (on 2018-02-24) provenance

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.

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.4.0

2 findings

HIGH Publisher changed: schickling → timsuchanek (on 2018-01-15) provenance

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

2 findings

HIGH Publisher changed: schickling → timsuchanek (on 2018-01-13) provenance

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

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

2 findings

HIGH Publisher changed: timsuchanek → schickling (on 2018-01-05) provenance

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

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

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