nodeca/pako

high speed zlib port to javascript, works in browser & node.js

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 25th, 2014
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 802
Total Stargazers: 6,114 (+0)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Pako is a JavaScript port of the zlib compression library that runs in both browser and Node.js environments.

The project solves the need for native compression and decompression in JavaScript by porting zlib's algorithms to pure JavaScript. It handles deflate, inflate, and related compression formats, allowing developers to work with compressed data without relying on native bindings or server-side processing. The implementation prioritizes speed while maintaining compatibility with the zlib format, making it suitable for scenarios where compression must happen client-side or in JavaScript runtimes.

Pako suits projects that need compression in the browser, such as applications handling file uploads, data transmission optimization, or working with compressed assets. It is also useful in Node.js environments where a pure JavaScript implementation is preferred over native modules. The tool works across both runtime contexts without code changes, which simplifies deployment for isomorphic applications. Developers should choose this when they need reliable zlib compatibility without external dependencies or native compilation steps.

The project maintains a stable codebase with infrequent but deliberate updates focused on bug fixes and compatibility improvements rather than feature expansion. Development activity shows attention to edge cases and real-world usage patterns, with issues addressed methodically. The maintainers prioritize correctness and performance in the existing feature set over adding new capabilities beyond standard zlib functionality.