popsicle-content-encoding

Popsicle middleware for supporting `Content-Encoding` compression

popsicle-content-encoding@1.0.0 was published on 2019-06-11. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All popsicle-content-encoding versions · Permanent reference to 1.0.0

Package specifications

Version1.0.0
License declarationMIT
Published2019-06-11T04:08:11.760Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.48 KiB
Published file count9
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars0
Repository forks0

Install popsicle-content-encoding 1.0.0

npm install popsicle-content-encoding@1.0.0
pnpm add popsicle-content-encoding@1.0.0
yarn add popsicle-content-encoding@1.0.0

Runtime dependencies

  • None declared

Peer requirements

Optional dependencies

  • None declared

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.

    Security-Policy10/10 — security policy file detected
    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
    Code-Review0/10 — Found 0/5 approved changesets -- score normalized to 0
    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
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness