compression — Greenflagged

Node.js compression middleware

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

dougwilsonulisesgasconwesleytodd

Keywords

compressiongzipdeflatemiddlewareexpressbrotlihttpstream

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Legacy version from long-standing expressjs maintainer; missing gitHead is expected for packages published before modern provenance tooling.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Sigstore provenance was not available when this version was published; stable for older versions of this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition from dougwilson to wesleytodd, a known Express.js TC member with long npm history.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): wesleytodd and ulisesgascon are known Express.js maintainers; legitimate team transition.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): Swapped 'accepts' for its own dependency 'negotiator'; net simplification, not a new attack surface.	ai	2026/04/23

Versions (showing 39 of 39)

Version	Deps	Published
1.8.1	7 / 11	2025-07-17
1.8.0	7 / 11	2025-02-10
1.7.5	7 / 11	2024-10-31
1.7.4	7 / 11	2019-03-18
1.7.3	7 / 11	2018-07-15
1.7.2	7 / 10	2018-02-19
1.7.1	7 / 10	2017-09-27
1.7.0	7 / 10	2017-07-11
1.6.2	6 / 7	2016-05-12
1.6.1	6 / 3	2016-01-20
1.6.0	6 / 3	2015-09-30
1.5.2	6 / 3	2015-07-31
1.5.1	6 / 3	2015-07-06
1.5.0	6 / 3	2015-06-10
1.4.4	6 / 3	2015-05-12
1.4.3	6 / 3	2015-03-15
1.4.2	6 / 3	2015-03-12
1.4.1	6 / 3	2015-02-15
1.4.0	6 / 3	2015-02-01
1.3.1	6 / 3	2015-02-01
1.3.0	6 / 3	2014-12-31
1.2.2	6 / 3	2014-12-10
1.2.1	6 / 3	2014-11-23
1.2.0	6 / 4	2014-10-17
1.1.2	6 / 4	2014-10-16
1.1.1	6 / 4	2014-10-13
1.1.0	6 / 4	2014-09-08
1.0.11	6 / 4	2014-08-11
1.0.10	6 / 4	2014-08-06
1.0.9	6 / 4	2014-07-21
1.0.8	5 / 4	2014-06-20
1.0.7	5 / 4	2014-06-12
1.0.6	4 / 4	2014-06-04
1.0.5	4 / 4	2014-06-04
1.0.4	4 / 4	2014-06-03
1.0.3	4 / 5	2014-05-30
1.0.2	3 / 4	2014-04-29
1.0.1	3 / 4	2014-03-08
1.0.0	3 / 4	2014-01-01

v1.8.0

2 findings

HIGH Publisher changed: dougwilson → wesleytodd (on 2025-02-10) provenance

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

2 findings

HIGH Publisher changed: dougwilson → ulisesgascon (on 2024-10-31) provenance

This version was published by a different npm account than previous versions on 2024-10-31. 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.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

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

INFO No provenance attestation provenance

[Accepted risk] 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.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

1 finding

INFO No provenance attestation provenance

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

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

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

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

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

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

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

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

v1.4.0

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

INFO No provenance attestation provenance

[Accepted risk] 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.2

1 finding

LOW No provenance attestation provenance

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

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

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

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

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

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

LOW No provenance attestation provenance

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

v1.0.8

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

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

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: jongleberry → dougwilson (on 2014-04-29) provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

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