compression-webpack-plugin 0.3.1

Prepare compressed versions of assets to serve them with Content-Encoding

compression-webpack-plugin@0.3.1 was published on 2016-03-26. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All compression-webpack-plugin versions · Permanent reference to 0.3.1 · View npm registry JSON · Latest release

Package specifications

Version0.3.1
License declarationNot declared
Published2016-03-26T15:58:06.030Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count3
Peer requirement count0
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies146
Repository stars1423
Repository forks108

Install compression-webpack-plugin 0.3.1

npm install compression-webpack-plugin@0.3.1
pnpm add compression-webpack-plugin@0.3.1
yarn add compression-webpack-plugin@0.3.1

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

Resolved dependency graph

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

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review7/10 — Found 17/24 approved changesets -- score normalized to 7
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness