pako
npmv3.0.1TypeScriptzlib port to javascript - fast, modularized, with browser support
Safe to adopt
Yes — pako scores well across adoption, maintenance, weight, supply chain, and licensing. 100.8M downloads per week and 2 known dependents. Last published 65 days ago. 3 releases in the last 2 years.
- AAdoption: grade A, Excellent.
100.8M downloads per week and 2 known dependents.
- AMaintenance: grade A, Excellent.
Last published 65 days ago. 3 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 2.4 MB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
(MIT AND Zlib) — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding pako to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the pako README.
deflate-pako x 14.27 ops/sec ±3.41% (37 runs sampled)
deflate-pako-zlib-hash x 10.60 ops/sec ±0.50% (29 runs sampled)
deflate-zlib x 30.30 ops/sec ±0.61% (51 runs sampled)
gzip-pako x 13.48 ops/sec ±0.50% (36 runs sampled)
inflate-pako x 138 ops/sec ±1.26% (75 runs sampled)
inflate-zlib x 397 ops/sec ±1.37% (81 runs sampled)
ungzip-pako x 125 ops/sec ±1.46% (73 runs sampled)pako vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
Dependencies
Declared by pako v3.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (10)
Used by
Popular packages that depend on pako.
Relationship graph
Dependencies (left) and dependents (right) of pako.
Frequently installed together
React is a JavaScript library for building user interfaces.
React package for working with the DOM.
An AST-based pattern checker for JavaScript.
TypeScript definitions for react-dom
A shim for the setImmediate efficient script yielding API
TypeScript execution environment and REPL for node.js, with source map support
A high-level API to automate web browsers
A basic but performant promise implementation
TypeScript definitions for node
Create, read and edit .zip files with JavaScript http://stuartk.com/jszip
TypeScript definitions for react
Release history
3 releases in the last two years, typically about 52 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.0.1latest | 2 months ago | 2.4 MB | (MIT AND Zlib) |
| 3.0.0 | 2 months ago | 2.4 MB | (MIT AND Zlib) |
| 2.2.0 | 2 months ago | 1.6 MB | (MIT AND Zlib) |
| 2.1.0 | 3 years ago | 1.6 MB | (MIT AND Zlib) |
| 2.0.4 | 5 years ago | 1.5 MB | (MIT AND Zlib) |
| 2.0.3 | 5 years ago | 1.5 MB | (MIT AND Zlib) |
| 2.0.2 | 5 years ago | 1.5 MB | (MIT AND Zlib) |
| 2.0.1 | 5 years ago | 1.5 MB | (MIT AND Zlib) |
| 2.0.0 | 5 years ago | 1.5 MB | (MIT AND Zlib) |
| 1.0.11 | 6 years ago | 770 KB | (MIT AND Zlib) |
| 1.0.10 | 7 years ago | 768 KB | (MIT AND Zlib) |
| 1.0.9 | 7 years ago | 767 KB | (MIT AND Zlib) |
| 1.0.8 | 7 years ago | 767 KB | (MIT AND Zlib) |
| 1.0.7 | 7 years ago | 766 KB | (MIT AND Zlib) |
| 1.0.6 | 9 years ago | — | (MIT AND Zlib) |
Overview
pako is an npm package that zlib port to javascript - fast, modularized, with browser support. It is extremely widely used, with about 100.8M downloads per week and 2 known dependents in the graph. The latest version is 3.0.1, released under the (MIT AND Zlib) license.
Who should use it
Teams working in the npm ecosystem who need zlib port to javascript - fast, modularized, with browser support and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (100.8M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license ((MIT AND Zlib)).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use pako?
Yes — pako scores well across adoption, maintenance, weight, supply chain, and licensing. 100.8M downloads per week and 2 known dependents. Last published 65 days ago. 3 releases in the last 2 years.
How do I install pako?
Run `npm install pako` to add pako to your npm project.
What license is pako released under?
pako is distributed under the (MIT AND Zlib) license.
How popular is pako?
pako has approximately 100,784,547 downloads per week and 2 known dependent packages.
Is pako still maintained?
The most recent release of pako (v3.0.1) was published 2 months ago.
Does pako run install scripts?
No. pako does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.