pako (MIT AND Zlib) 31 versions

pako

npm Repository Homepage

zlib port to javascript - fast, modularized, with browser support

31

Versions

(MIT AND Zlib)

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

vitaly

Keywords

zlibdeflateinflategzip

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): pako 0.0.0 is the legitimate first release of a 12-year-old zlib library; the 0.0.0 version is not indicative of malicious intent for this established package.	ai	2026/04/22
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is in benchmark/benchmark.js, a dev-only benchmarking tool that loads impl files for comparison. Not runtime code and not a security concern.	ai	2026/04/22
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): The 127.0.0.1 reference is in Gruntfile.js as a localhost test server URL for browser testing — a standard dev tooling pattern, not a malicious endpoint. Stable false positive for this package.	ai	2026/04/22
typosquat	typosquat.levenshtein:pino	AI (typosquat): pako is a well-established zlib compression library; name similarity to 'pino' (a logging library) is purely coincidental with no impersonation intent. Stable false positive for this package.	ai	2026/04/21

Versions (showing 31 of 31)

Version	Deps	Published
2.1.0	0 / 13	2022-11-07
2.0.4	0 / 13	2021-07-29
2.0.3	0 / 13	2021-01-09
2.0.2	0 / 13	2020-11-18
2.0.1	0 / 13	2020-11-17
2.0.0	0 / 13	2020-11-17
1.0.11	0 / 11	2020-01-29
1.0.10	0 / 11	2019-02-28
1.0.9	0 / 11	2019-02-28
1.0.8	0 / 10	2019-01-14
1.0.7	0 / 15	2018-11-29
1.0.6	0 / 15	2017-09-14
1.0.5	0 / 18	2017-03-26
1.0.4	0 / 15	2016-12-15
1.0.3	0 / 15	2016-07-25
1.0.2	0 / 15	2016-07-21
1.0.1	0 / 15	2016-04-01
1.0.0	0 / 15	2016-02-17
0.2.9	0 / 15	2016-07-21
0.2.8	0 / 15	2015-09-14
0.2.7	0 / 15	2015-06-09
0.2.6	0 / 14	2015-03-24
0.2.5	0 / 14	2014-07-19
0.2.4	0 / 14	2014-07-07
0.2.3	0 / 14	2014-06-08
0.2.2	0 / 15	2014-06-04
0.2.1	0 / 15	2014-05-01
0.2.0	0 / 15	2014-04-18
0.1.1	0 / 15	2014-03-20
0.1.0	0 / 15	2014-03-15
0.0.0	0 / 5	2014-02-19

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

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.

v1.0.3

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.

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

v1.0.1

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.

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.

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

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.

v0.2.7

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.

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

v0.2.5

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.

v0.2.4

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.

v0.2.3

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.

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

v0.2.1

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.

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

v0.1.1

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.

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

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