express-graphql — Greenflagged

Production ready GraphQL HTTP middleware.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

leebyroni1gwincentjosephsavonakassensasiandrummerags-

Keywords

expressrestifyconnecthttpgraphqlmiddlewareapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Well-established package under graphql GitHub org with trusted publisher; missing gitHead is a benign publish-environment change.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from bundling GraphiQL IDE assets inline in renderGraphiQL.js — expected for this package's architecture.	ai	2026/04/24
source-diff	obfuscated-file:renderGraphiQL.js	AI (source-diff): renderGraphiQL.js bundles the GraphiQL IDE frontend (React app + CSS) inline for serving without extra HTTP requests. This is the documented architecture.	ai	2026/04/24
source-diff	source-size-dropped	AI (source-diff): Package ships compiled dist/ only; source size metric on src/ is irrelevant for published artifact.	ai	2026/04/24
phantom-deps	phantom-dep:accepts	AI (phantom-deps): Used via compiled dist output; legitimate HTTP middleware dependency for express-graphql.	ai	2026/04/24
phantom-deps	phantom-dep:http-errors	AI (phantom-deps): Used via compiled dist output; legitimate dependency for HTTP error handling.	ai	2026/04/24
phantom-deps	phantom-dep:content-type	AI (phantom-deps): Used via compiled dist output; legitimate dependency for content-type parsing.	ai	2026/04/24
phantom-deps	phantom-dep:raw-body	AI (phantom-deps): Used via compiled dist output; legitimate dependency for parsing request bodies.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition from leebyron to ags- (Ivan Goncharov), a well-known GraphQL ecosystem maintainer with strong npm track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): asiandrummer and kassens are known GraphQL/Meta engineers; legitimate team expansion for the official graphql org package.	ai	2026/04/24
source-diff	obfuscated-file:dist/renderGraphiQL.js	AI (source-diff): dist/renderGraphiQL.js is a Babel-compiled HTML template renderer for GraphiQL IDE; long lines are inline HTML strings, not obfuscation. Stable false positive for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): express-graphql predates Sigstore provenance; publisher is well-established with strong track record.	ai	2026/04/24

Versions (showing 35 of 35)

Version	Deps	Published
0.12.0	4 / 0	2020-11-19
0.11.0	4 / 0	2020-07-06
0.10.2	4 / 0	2020-07-05
0.9.0	4 / 0	2019-07-15
0.8.0	4 / 27	2019-04-14
0.7.1	4 / 27	2018-10-29
0.7.0	4 / 27	2018-10-29
0.6.12	4 / 27	2018-02-19
0.6.11	4 / 27	2017-08-29
0.6.7	4 / 27	2017-07-28
0.6.5	4 / 26	2017-05-15
0.6.4	4 / 27	2017-03-31
0.6.3	4 / 27	2017-02-01
0.6.2	4 / 27	2017-01-24
0.6.1	4 / 29	2016-11-12
0.6.0	4 / 30	2016-11-12
0.5.1	3 / 19	2016-04-12
0.5.0	3 / 19	2016-04-08
0.4.13	3 / 19	2016-03-25
0.4.12	3 / 19	2016-03-24
0.4.11	3 / 19	2016-03-24
0.4.10	3 / 19	2016-03-11
0.4.9	3 / 19	2016-02-03
0.4.8	3 / 19	2016-02-03
0.4.7	3 / 19	2016-02-03
0.4.6	3 / 19	2016-02-03
0.4.5	3 / 19	2015-12-01
0.4.4	3 / 19	2015-11-11
0.4.3	3 / 19	2015-11-11
0.4.2	3 / 19	2015-11-02
0.4.0	3 / 19	2015-10-01
0.3.0	3 / 17	2015-08-14
0.2.0	3 / 17	2015-08-12
0.1.1	3 / 17	2015-08-11
0.1.0	4 / 16	2015-08-10

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: i1g.

INFO No provenance attestation provenance

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

v0.10.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: i1g.

LOW No provenance attestation provenance

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

v0.9.0

4 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: i1g.

HIGH Publisher changed: ags- → i1g (on 2019-07-15) provenance

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

HIGH New obfuscated file: renderGraphiQL.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.8.0

1 finding

INFO No provenance attestation provenance

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

v0.7.1

1 finding

INFO No provenance attestation provenance

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

v0.7.0

2 findings

HIGH Publisher changed: leebyron → ags- (on 2018-10-29) provenance

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.

INFO No provenance attestation provenance

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

v0.6.12

1 finding

INFO No provenance attestation provenance

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

v0.6.11

1 finding

INFO No provenance attestation provenance

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

v0.6.7

1 finding

INFO No provenance attestation provenance

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

v0.6.5

1 finding

INFO No provenance attestation provenance

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

v0.6.4

1 finding

INFO No provenance attestation provenance

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

v0.6.3

1 finding

INFO No provenance attestation provenance

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

v0.6.2

1 finding

INFO No provenance attestation provenance

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

v0.6.1

1 finding

INFO No provenance attestation provenance

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

v0.6.0

1 finding

INFO No provenance attestation provenance

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

v0.5.1

1 finding

INFO No provenance attestation provenance

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

v0.5.0

1 finding

INFO No provenance attestation provenance

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

v0.4.13

1 finding

INFO No provenance attestation provenance

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

v0.4.12

1 finding

INFO No provenance attestation provenance

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

v0.4.11

1 finding

INFO No provenance attestation provenance

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

v0.4.10

1 finding

INFO No provenance attestation provenance

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

v0.4.9

1 finding

INFO No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

INFO No provenance attestation provenance

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

v0.4.6

1 finding

INFO No provenance attestation provenance

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

v0.4.5

1 finding

INFO No provenance attestation provenance

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

v0.4.4

1 finding

INFO No provenance attestation provenance

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

v0.4.3

1 finding

INFO No provenance attestation provenance

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

v0.4.2

2 findings

HIGH New obfuscated file: dist/renderGraphiQL.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.4.0

2 findings

HIGH New obfuscated file: dist/renderGraphiQL.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v0.3.0

1 finding

INFO No provenance attestation provenance

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

v0.2.0

1 finding

INFO No provenance attestation provenance

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

v0.1.1

1 finding

INFO No provenance attestation provenance

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

v0.1.0

1 finding

INFO No provenance attestation provenance

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