connect-timeout 0.0.1

Adds timeouts to connect responses

connect-timeout@0.0.1 was published on 2011-02-09. 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.2.0.

All connect-timeout versions · Permanent reference to 0.0.1 · Latest release

Package specifications

Version0.0.1
License declarationNot declared
Published2011-02-09T13:46:53.738Z
Node.js requirement>= 0.2.0
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
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 entryindex
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars320
Repository forks51

Install connect-timeout 0.0.1

npm install connect-timeout@0.0.1
pnpm add connect-timeout@0.0.1
yarn add connect-timeout@0.0.1

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-Review2/10 — Found 6/26 approved changesets -- score normalized to 2
    Binary-Artifacts10/10 — no binaries found in the repo
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
    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
    Security-Policy10/10 — security policy file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    SAST9/10 — SAST tool detected but not run on all commits

    Evidence and freshness