connect 2.5.0
High performance middleware framework
connect@2.5.0 was published on 2012-09-27. Its manifest declares 9 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.5.0.
Deprecated: connect 2.x series is deprecated
All connect versions · Permanent reference to 2.5.0 · Latest release
Package specifications
| Version | 2.5.0 |
|---|---|
| License declaration | Not declared |
| Published | 2012-09-27T19:38:07.906Z |
| Node.js requirement | >= 0.5.0 |
| Type declarations | Not declared |
| Runtime dependency count | 9 |
| 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 | index |
| Side effects declaration | Not declared |
| Direct advisories | 3 |
| Resolved graph dependencies | 12 |
| Repository stars | 9871 |
| Repository forks | 1078 |
Install connect 2.5.0
npm install connect@2.5.0 pnpm add connect@2.5.0 yarn add connect@2.5.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.
- bytes@0.1.0 — direct
- cookie@0.0.4 — direct
- crc@0.2.0 — direct
- debug@4.4.3 — direct
- formidable@1.0.11 — direct
- fresh@0.1.0 — direct
- mime@1.2.6 — indirect
- ms@2.1.3 — indirect
- pause@0.0.1 — direct
- qs@0.5.1 — direct
- range-parser@0.0.4 — indirect
- send@0.0.4 — direct
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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Code-Review | 0/10 — Found 1/30 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Security-Policy | 10/10 — security policy file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/connect/2.5.0 — retrieved 2026-10-29T11:13:48.348Z
- https://api.deps.dev/v3/projects/github.com%2Fsenchalabs%2Fconnect — retrieved 2026-10-29T07:15:39.066Z
- https://api.deps.dev/v3/systems/npm/packages/connect/versions/2.5.0 — retrieved 2026-10-29T11:13:48.867Z
- https://api.deps.dev/v3/systems/npm/packages/connect/versions/2.5.0:dependencies — retrieved 2026-10-29T11:13:48.894Z