compress-commons 1.1.0

a library that defines a common interface for working with archive formats within node

compress-commons@1.1.0 was published on 2016-08-27. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.0.

All compress-commons versions · Permanent reference to 1.1.0 · Latest release

Package specifications

Version	1.1.0
License declaration	MIT
Published	2016-08-27T18:27:13.549Z
Node.js requirement	>= 0.10.0
Type declarations	Not declared
Runtime dependency count	4
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	Not supplied
Published file count	Not supplied
Package type	Not declared
ES module entry	Not declared
Default entry	lib/compress-commons.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	16
Repository stars	17
Repository forks	33

Install compress-commons 1.1.0

npm install compress-commons@1.1.0
pnpm add compress-commons@1.1.0
yarn add compress-commons@1.1.0

Runtime dependencies

Peer requirements

None declared

Optional dependencies

None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

base64-js@1.5.1 — indirect
buffer@5.7.1 — indirect
buffer-crc32@0.2.13 — direct
core-util-is@1.0.3 — indirect
crc@3.8.0 — indirect
crc32-stream@1.0.1 — direct
ieee754@1.2.1 — indirect
inherits@2.0.4 — indirect
isarray@1.0.0 — indirect
normalize-path@2.1.1 — direct
process-nextick-args@2.0.1 — indirect
readable-stream@2.3.8 — direct
remove-trailing-separator@1.1.0 — indirect
safe-buffer@5.1.2 — indirect
string_decoder@1.1.1 — indirect
util-deprecate@1.0.2 — indirect

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained	0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Code-Review	0/10 — Found 0/7 approved changesets -- score normalized to 0
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Binary-Artifacts	10/10 — no binaries found in the repo
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies	4/10 — dependency not pinned by hash detected -- score normalized to 4
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy	0/10 — security policy file not detected
Fuzzing	0/10 — project is not fuzzed
License	10/10 — license file detected
SAST	0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness

https://registry.npmjs.org/compress-commons/1.1.0 — retrieved 2026-10-29T08:51:19.082Z
https://api.deps.dev/v3/projects/github.com%2Farchiverjs%2Fnode-compress-commons — retrieved 2026-10-29T06:02:55.034Z
https://api.deps.dev/v3/systems/npm/packages/compress-commons/versions/1.1.0 — retrieved 2026-10-29T08:51:19.840Z
https://api.deps.dev/v3/systems/npm/packages/compress-commons/versions/1.1.0:dependencies — retrieved 2026-10-29T08:51:19.865Z