on-headers

Execute a listener when a response is about to write headers

on-headers@1.1.0 was published on 2025-07-17. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.8.

All on-headers versions · Permanent reference to 1.1.0

Package specifications

Version1.1.0
License declarationMIT
Published2025-07-17T15:41:31.684Z
Node.js requirement>= 0.8
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size8.64 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars163
Repository forks35

Install on-headers 1.1.0

npm install on-headers@1.1.0
pnpm add on-headers@1.1.0
yarn add on-headers@1.1.0

Runtime dependencies

  • None declared

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.

    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.

    Code-Review4/10 — Found 12/28 approved changesets -- score normalized to 4
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Binary-Artifacts10/10 — no binaries found in the repo
    Maintained1/10 — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
    Pinned-Dependencies2/10 — dependency not pinned by hash detected -- score normalized to 2
    Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
    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
    Security-Policy9/10 — security policy file detected
    SAST8/10 — SAST tool detected but not run on all commits

    Evidence and freshness