compressible — Greenflagged

Compressible Content-Type / mime checking

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

dougwilsonfishrock123jongleberry

Keywords

compressgzipmimecontent-type

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): 2014-era publish; gitHead tracking was inconsistent in older npm versions. Not a concern for this well-established package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): fishrock123 is a listed contributor and known Node.js core contributor in the jshttp org; legitimate maintainer.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2014, before Sigstore provenance existed. Stable for this package's older versions.	ai	2026/04/24

Versions (showing 26 of 26)

Version	Deps	Published
2.0.18	1 / 9	2020-01-06
2.0.17	1 / 9	2019-04-24
2.0.16	1 / 9	2019-02-18
2.0.15	1 / 9	2018-09-17
2.0.14	1 / 9	2018-06-05
2.0.13	1 / 9	2018-02-18
2.0.12	1 / 9	2017-10-20
2.0.11	1 / 9	2017-07-28
2.0.10	1 / 7	2017-03-24
2.0.9	1 / 6	2016-10-31
2.0.8	1 / 6	2016-05-12
2.0.7	1 / 2	2016-01-19
2.0.6	1 / 2	2015-09-30
2.0.5	1 / 2	2015-07-31
2.0.4	1 / 2	2015-07-02
2.0.3	1 / 2	2015-06-08
2.0.2	1 / 2	2015-02-01
2.0.1	1 / 2	2014-10-04
2.0.0	1 / 2	2014-09-02
1.1.1	0 / 1	2014-08-06
1.1.0	0 / 1	2014-06-04
1.0.1	0 / 4	2014-03-21
1.0.0	0 / 4	2014-01-01
0.2.0	0 / 1	2013-12-23
0.1.1	0 / 1	2013-12-19
0.1.0	0 / 1	2013-12-19

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

3 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: fishrock123.

HIGH Publisher changed: dougwilson → fishrock123 (on 2014-10-04) provenance

This version was published by a different npm account than previous versions on 2014-10-04. 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.0.0

3 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: fishrock123.

HIGH Publisher changed: dougwilson → fishrock123 (on 2014-09-02) provenance

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

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: fishrock123 → dougwilson (on 2014-08-06) provenance

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

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

INFO No provenance attestation provenance

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